From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Movement commands
Date: 02 Mar 1999 16:54:19 +0100 [thread overview]
Message-ID: <vafaexvnaz8.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "02 Mar 1999 16:02:33 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> But what should `45 E' do, then? Since `E' doesn't move, should
> `45 E' mark the same article as expirable 45 times?
See my previous message. A prefix argument doesn't really make sense
for the non-moving variants. But maybe gnus-summary-mark-as-foo-next
should mark the next N articles and move forward N articles; wherwas
gnus-summary-mark-as-foo-dont-move should mark N articles and move
forward N-1 articles? Hm.
kai
--
I like _\bb_\bo_\bt_\bh kinds of music.
prev parent reply other threads:[~1999-03-02 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-01 15:20 Kai.Grossjohann
1999-03-02 15:02 ` Lars Magne Ingebrigtsen
1999-03-02 15:52 ` Kai.Grossjohann
1999-03-06 18:21 ` Lars Magne Ingebrigtsen
1999-03-02 15:54 ` Kai.Grossjohann [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=vafaexvnaz8.fsf@ramses.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).