From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: Need help debugging window configuration
Date: Sat, 28 Jul 2001 02:12:32 -0400 [thread overview]
Message-ID: <m34rrxinu7.fsf@bombay.dyndns.org> (raw)
In-Reply-To: <2n3d7hopgj.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Fri, 27 Jul 2001 17:41:00 -0700")
[Apologies to ShengHuo if he sees this twice. I replied instead of
following up.]
Summary: I had a problem with SPC in the summary buffer.
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Nevin Kapur <nevin@jhu.edu> writes:
>
>> With this, the SPC key in the *Summary* buffer behaves weirdly for
>> *some* articles. That is, if I press SPC, I get a blank *Article*
>> buffer, indicating that I reached the end of the article, even though
>> there is more there. This can be confirmed by using the BS key. The
>> following screenshots explain this situation:
>>
>> Here is the original article:
>> http://www.mts.jhu.edu/~kapur/SPACE_bug/space-1.png
>> Now I press SPC:
>> http://www.mts.jhu.edu/~kapur/SPACE_bug/space-2.png
>> Now I press BS:
>> http://www.mts.jhu.edu/~kapur/SPACE_bug/space-3.png
>>
>> Notice that the last screen of article never showed up.
> I can't reproduce this bug. Anyone?
I have a better handle on the bug now. It is minimally triggered by
these lines:
(gnus-add-configuration
'(article
(horizontal 1.0
(vertical 25 (group 1.0))
(vertical 1.0
(summary 0.16 point)
(article 1.0)))))
(setq gnus-always-force-window-configuration t)
(setq gnus-treat-display-xface 'head)
Now if there is an article which is just a little more than 1 screen,
I get the behavior describe above. Maybe it's not a bug. Perhaps one's
not supposed to use these options together.
> How about other version of XEmacs?
I can reproduce this on XEmacs 21.1.14, 21.4.3 with Gnus 5.8.8 and
Oort.
--
Nevin
prev parent reply other threads:[~2001-07-28 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 13:33 Nevin Kapur
2001-07-23 13:52 ` Nevin Kapur
2001-07-28 0:41 ` ShengHuo ZHU
2001-07-28 6:12 ` Nevin Kapur [this message]
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=m34rrxinu7.fsf@bombay.dyndns.org \
--to=nevin@jhu.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).