From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: can't scroll one line if only *Article* buffer showing
Date: Tue, 16 Nov 2010 19:17:53 +0100 [thread overview]
Message-ID: <m37hgdw2su.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87hbfhvpz9.fsf@jidanni.org>
jidanni@jidanni.org writes:
> Yes. Reading with only the *Article* buffer visible, one quickly notices
> that not all the basic keys have been bound yet. For example, it is so
> frustrating that one can only scroll up or down several lines. If one
> wants to scroll down one line, he must open back up the Summary buffer
> just to do that.
If you scroll up/down buffers one line a lot, then I'd suggest binding
some key globally to `scroll-up-line'.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-11-16 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 17:33 jidanni
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 [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=m37hgdw2su.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).