From: nobrowser@gmail.com
Subject: Moving after marking
Date: 27 Sep 2006 09:13:12 -0700 [thread overview]
Message-ID: <1159373592.497448.19190@e3g2000cwe.googlegroups.com> (raw)
Hi, looking at the documentation for `gnus-summary-goto-unread':
>>>
If t, many commands will go to the next unread article.
This applies to marking commands as well as other commands that
"naturally" select the next article, like, for instance, `SPC' at
the end of an article.
If nil, the marking commands do NOT go to the next unread article
(they go to the next article instead). If `never', commands that
usually go to the next unread article, will go to the next article,
whether it is read or not.
<<<
But, actually, a lot of the time (almost always when explicitly
marking, in fact) I'd prefer _not to move anywhere at all_. I remember
from the old days that Rmail could be instructed that way, but I don't
see how to do it for Gnus. Note that just saving point or setting an
Emacs mark is not a solution, because moving also has the side effect
of making the next article read. TIA for ideas.
next reply other threads:[~2006-09-27 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 16:13 nobrowser [this message]
2006-10-05 23:08 ` nobrowser
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=1159373592.497448.19190@e3g2000cwe.googlegroups.com \
--to=nobrowser@gmail.com \
/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).