Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "nobrowser" <nobrowser@gmail.com>
Subject: Re: Moving after marking
Date: 5 Oct 2006 16:08:51 -0700	[thread overview]
Message-ID: <1160089731.122116.143580@h48g2000cwc.googlegroups.com> (raw)
In-Reply-To: <1159373592.497448.19190@e3g2000cwe.googlegroups.com>


nobrowser@gmail.com wrote:

> 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.

I found a workaround for the most common case, marking the current
article read (the 'r' mark).  The workaround is C-SPC C-u C-w.  Still,
it is a bit too long.  Does nobody else really find this to be a
nuisance?

      reply	other threads:[~2006-10-05 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-27 16:13 nobrowser
2006-10-05 23:08 ` nobrowser [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=1160089731.122116.143580@h48g2000cwc.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).