From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-auto-center-summary off-center
Date: 28 Sep 1999 02:10:08 -0400 [thread overview]
Message-ID: <2n3dvzefcv.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Stainless Steel Rat's message of "27 Sep 1999 22:22:08 -0400"
>>>>> "Rat" == Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
Rat> What I think is happening is that the mode line bezel makes the
Rat> mode line "taller" than a line of text. XEmacs laps the bezel
Rat> over the buffer text, producing your "half-chopped-off line".
Rat> This is not a bug, it is normal and correct behaviour for XEmacs.
Rat> When you select the last message in the summary buffer, XEmacs
Rat> scrolls up the entire window by 1 line so that the full text of
Rat> the line is displayed without being cropped.
Rat> What happens if you reduce the size of the mode line bezel to 0
Rat> with `(set-specifier modeline-shadow-thickness 0)'? This will
Rat> make XEmacs' mode lines look like FSF Emacs mode lines and should
Rat> make the cropping problem go away.
Rat> I normally use XEmacs without mode line bezels. Your "fix"
Rat> really screws up the display, I am sorry to say.
Unfortunately, it is not the case. The mode line bezel does not make
Gnus get wrong answer. In XEmacs, Gnus use `window-displayed-height'
to calculate the height of the window. I guess
`window-displayed-height' has count the thickness of the mode line
bezel. And I never said it is a bug of XEmacs.
But, it is the *displayed* height. When Gnus scrolls the summary
lines, some lines leaves the windows, and other lines enter. Then the
window-displayed-height may change, since the font size of lines may
be different. In the case that the last line is the current line, Gnus
may scroll it half-chopped-off or even out of the window. This is the
bug I tried to fix.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-09-28 6:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-20 2:54 Stainless Steel Rat
1999-08-28 1:03 ` Stainless Steel Rat
1999-09-24 18:33 ` Lars Magne Ingebrigtsen
1999-09-24 20:39 ` Stainless Steel Rat
1999-09-24 21:20 ` Shenghuo ZHU
1999-09-24 23:36 ` Stainless Steel Rat
1999-09-25 5:23 ` Shenghuo ZHU
1999-09-25 10:16 ` Lars Magne Ingebrigtsen
1999-09-28 1:22 ` Shenghuo ZHU
1999-09-28 2:22 ` Stainless Steel Rat
1999-09-28 2:49 ` Stainless Steel Rat
1999-09-28 6:10 ` Shenghuo ZHU [this message]
1999-09-28 14:46 ` Stainless Steel Rat
1999-09-29 8:59 ` Jan Vroonhof
1999-09-29 16:44 ` Stainless Steel Rat
1999-11-05 22:58 ` Lars Magne Ingebrigtsen
1999-09-30 10:52 ` Jan Vroonhof
1999-09-30 18:44 ` Stainless Steel Rat
1999-10-01 12:45 ` Jan Vroonhof
1999-09-26 18:19 ` Shenghuo ZHU
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=2n3dvzefcv.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).