From: jidanni@jidanni.org
To: ding@gnus.org
Subject: can't scroll one line if only *Article* buffer showing
Date: Sat, 13 Nov 2010 01:33:24 +0800 [thread overview]
Message-ID: <871v6q30rf.fsf@jidanni.org> (raw)
Normally to scroll an article just one line, one hits RET (gnus-summary-scroll-up).
However, after using
h runs the command gnus-summary-select-article-buffer
(with `gnus-widen-article-buffer' set, to show only the article buffer)
RET just gives
widget-button-press: Buffer is read-only: #<buffer *Article gmane.linux.debian.user.news*>
Maybe one could say it is due to my
http://jidanni.org/comp/configuration/ using emacs-w3m or something.
However widget-button-press should be smart enough to know that when the
cursor is not upon a link it should just act like RET does in the
*Summary* buffer.
One would think that J (w3m-scroll-up-1) would do what we want, but we
find in gnus *Article* buffer that is not bound, which reveals another
bug: J, i, etc. unbound keys, when typed into the *Article* buffer,
cause it to fly back to the top of the article, instead of having the
article remain in place.
By the way, in pure emacs-w3m, if J is the way to scroll one line, why
is there no w3m-scroll-down-1 function/binding?
$ apt-show-versions emacs-snapshot w3m-el-snapshot
emacs-snapshot/sid uptodate 1:20101030-1
w3m-el-snapshot/unstable uptodate 1.4.400+0.20100725-1
next reply other threads:[~2010-11-12 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 17:33 jidanni [this message]
2010-11-14 16:02 ` Lars Magne Ingebrigtsen
2010-11-14 19:11 ` Rupert Swarbrick
2010-11-14 19:18 ` Lars Magne Ingebrigtsen
2010-11-16 4:42 ` jidanni
2010-11-16 5:14 ` jidanni
2010-11-16 18:16 ` Lars Magne Ingebrigtsen
2010-11-16 18:17 ` Lars Magne Ingebrigtsen
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=871v6q30rf.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).