From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: beyond last article in the *Summary* buffer
Date: Tue, 31 Aug 2010 22:34:25 -0400 [thread overview]
Message-ID: <84wrr6p4y6.fsf@davestoy.home> (raw)
In-Reply-To: <87occisqp1.fsf@myles.home.wjsullivan.net> (John Sullivan's message of "Tue, 31 Aug 2010 09:16:26 -0700")
> Steinar Bang <sb@dod.no> writes:
>>>>>>> jidanni@jidanni.org:
>>
>>> Try this in the *Summary* buffer:
M-> (translated from <escape> >) runs the command end-of-buffer
>>> then
>>> p runs the command gnus-summary-prev-unread-article
>>
>>> Notice how we have gone to the 2nd to last article, not the last
>>> article as would be expected.
>>
>> I ended up in the last article, as I expected.
> Me too.
I got jidanni's behavior. Also just pressing space on that empty last
line opens the last article suggesting that it is indeed considered
"current" at that point.
--
Dave Goldberg
david.goldberg6@verizon.net
prev parent reply other threads:[~2010-09-01 2:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 8:48 jidanni
2010-08-31 10:33 ` Steinar Bang
2010-08-31 16:16 ` John Sullivan
2010-09-01 2:34 ` Dave Goldberg [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=84wrr6p4y6.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--cc=ding@gnus.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).