Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: [Fixed] uneven summary lines
Date: Sun, 20 Jan 2002 11:16:42 +1100	[thread overview]
Message-ID: <874rlhswph.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <m3y9iurpzw.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 19 Jan 2002 22:26:59 +0100")

On Sat, 19 Jan 2002, Lars Magne Ingebrigtsen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
> 
>> By the way, why is the default value of
>> `gnus-use-correct-string-widths' t only for XEmacs?
>> The value t is fit for me irrespective of the Emacs version, and
>> nil is fit for people irrespective of the Emacs version, either.
> 
> I thought what we were trying to fix with
> `gnus-use-correct-string-widths' was the tendency of `format' under
> Emacs and XEmacs to return different lengths.

[...]

> However, there may be other subtle issues in the gnus-spec code that
> introduces other problems that `gnus-use-correct-string-widths' fixes,
> but my feeling is that these problems are probably bugs in Gnus in the
> Emacs case...

My recollection, and why the code got written initially, was the
incorrect width used for `cut' forms, pretty much, and for padding in
the summary buffer.

        Daniel

-- 
One likes to believe in the freedom of music,
But glittering prizes and endless compromises
Shatter the illusion of integrity.
        -- Rush, _The Spirit of Radio_, 1980



  reply	other threads:[~2002-01-20  0:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 12:52 Katsumi Yamaoka
2002-01-19 21:26 ` Lars Magne Ingebrigtsen
2002-01-20  0:16   ` Daniel Pittman [this message]
2002-01-20  0:27     ` Lars Magne Ingebrigtsen
2002-01-20  2:11       ` Daniel Pittman
2002-01-20  2:23         ` Lars Magne Ingebrigtsen
2002-01-20 10:48           ` Daniel Pittman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874rlhswph.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).