From: David Hedbor <david@hedbor.org>
Subject: Re: New in Gnus v5.8.3 - display problems
Date: 08 Jan 2000 22:46:02 -0800 [thread overview]
Message-ID: <m3g0w7kaj9.fsf@nyarlathotep.home.hedbor.org> (raw)
In-Reply-To: Shenghuo ZHU's message of "08 Jan 2000 22:11:47 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> >>>>> "Dmitry" == Dmitry Yaitskov <dimas@home.com> writes:
>
> Dmitry> Hi,
>
> Dmitry> Using XEmacs 21.2.b26, I have the following problem which
> Dmitry> appeared in 5.8.3 (worked fine in 5.8.2): If the summary
> Dmitry> buffer is shown full-screen, pressing enter to read a message
> Dmitry> in it results in cursor losing its place in the
> Dmitry> summary(positioning over another unrelated message) after the
> Dmitry> screen is split into two to show the message text.
>
> Dmitry> Going back to last millenium version... :)
>
> I always find this problem happen when it is the last article in the
> summary buffer (the number of articles shown in buffer is larger than
> the height of summary window).
>
> Besides this, I also find another weird display problem. When enter
> the last group shown in the group window, then read all articles and
> exit the summary buffer, the cursor is not on the next unread group.
>
> Both problems only happen recently in XEmacs. Since b26 was also
> released in this millennium, I am wondering whether this is a bug in
> XEmacs 21.2.b26 and whether 5.8.2 really works fine in
> b26. set-window-start is a suspicious function.
>
> Did anyone test these problems in other version of XEmacs?
Well, I get the original problem with xemacs 21.1 so that one is
atleast not related to the above betaversion.
--
[ Below is a random fortune, which is unrelated to the above message. ]
I hate dying.
-- Dave Johnson
prev parent reply other threads:[~2000-01-09 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-06 8:02 Dmitry Yaitskov
2000-01-07 1:41 ` David Hedbor
2000-01-09 3:11 ` Shenghuo ZHU
2000-01-09 6:46 ` David Hedbor [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=m3g0w7kaj9.fsf@nyarlathotep.home.hedbor.org \
--to=david@hedbor.org \
/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).