From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: minor bug in digests
Date: 17 Oct 1998 22:39:26 +0200 [thread overview]
Message-ID: <m3pvbqx6rl.fsf@sparky.gnus.org> (raw)
In-Reply-To: Colin Rafferty's message of "13 Oct 1998 16:08:12 -400"
Colin Rafferty <craffert@ms.com> writes:
> When I enter a digest group (C-d), and then leave it (q), point has
> been moved to the next line in the *Summary*. The next message is not
> selected (and it shouldn't be), but I should really be on the current
> message (especially since that is the one showing in *Article*).
This was changed on the behest of someone who wanted the `q' command
to advance in the summary buffer, since it does that it the group
buffer as well. Seems logical to me.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-10-17 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-13 20:08 Colin Rafferty
1998-10-17 20:39 ` 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=m3pvbqx6rl.fsf@sparky.gnus.org \
--to=larsi@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).