From: jidanni@jidanni.org
To: ding@gnus.org
Subject: gnus-article-goto-next-page loops back up on last article
Date: Sat, 12 Nov 2011 19:21:49 +0800 [thread overview]
Message-ID: <87k475egc2.fsf@jidanni.org> (raw)
Make the Article buffer become the whole window with "h" or C-x 0.
[h runs the command gnus-summary-select-article-buffer]
Now browse to the bottom of the bottom article.
Now hit SPC.
Now we are back at the top of the bottom article.
If we had done this from the Summary buffer, we would still be at the
bottom of that article, and not back up at the top thinking we were now
reading a new article like some boob.
So SPC runs the command gnus-article-goto-next-page has a bug.
Whereas SPC runs the command gnus-summary-next-page is OK.
Of course it may be due to my
http://jidanni.org/comp/configuration/.gnus.el
next reply other threads:[~2011-11-12 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 11:21 jidanni [this message]
2011-11-12 22:12 ` Peter Münster
2012-01-03 22:30 ` Lars Magne Ingebrigtsen
2012-01-05 14:06 ` jidanni
2012-01-11 22:47 ` Eric S Fraga
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=87k475egc2.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--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).