From: Hannu Koivisto <azure@iki.fi>
Subject: Re: Exiting a group without moving to the next unread group?
Date: 03 Feb 2001 15:22:27 +0200 [thread overview]
Message-ID: <871ytflx4c.fsf@lynx.ionific.com> (raw)
In-Reply-To: <87k87fjzao.fsf@lynx.ionific.com> (Hannu Koivisto's message of "28 Jan 2001 20:40:15 +0200")
Hannu Koivisto <azure@iki.fi> writes:
| The subject pretty much says it all -- how can I exit a group so
| that Gnus doesn't move to the next unread group in the group
| buffer?
Since there didn't seem to be a way, I implemented one (yes, it is
a bit hackish):
(defun gnus-summary-exit-dont-move (&optional temporary)
"Like `gnus-summary-exit' but does not move to the next unread group."
(interactive)
(flet ((gnus-group-next-unread-group (n &rest ignored)
n))
(gnus-summary-exit temporary)))
--
Hannu
prev parent reply other threads:[~2001-02-03 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 18:40 Hannu Koivisto
2001-02-03 13:22 ` Hannu Koivisto [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=871ytflx4c.fsf@lynx.ionific.com \
--to=azure@iki.fi \
/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).