From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Movement commands
Date: 02 Mar 1999 16:02:33 +0100 [thread overview]
Message-ID: <m3k8x0c4ty.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "01 Mar 1999 16:20:49 +0100"
Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> (By orthogonality I mean that it should be possible to specify the
> following movement behaviors for *all* marking commands: don't move,
> move to the next/previous message, move to the next/previous unread
> message. Currently, different commands behave in different ways.)
Well, that's doable. For instance:
'(("d" next-unread)
("D" prev)
("E" no-move)
...
)
(Or something.)
But what should `45 E' do, then? Since `E' doesn't move, should
`45 E' mark the same article as expirable 45 times?
And if we cover the marking commands this way, shouldn't the selection
commands also be covered?
`((" " select-next-unread)
("\r" no-move)
...
)
I want SPC to go to the next group if I tap `SPC' on the last bit of
the last article in a group, but not otherwise, and how does one
specify that?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-03-02 15:02 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 [this message]
1999-03-02 15:52 ` Kai.Grossjohann
1999-03-06 18:21 ` Lars Magne Ingebrigtsen
1999-03-02 15:54 ` Kai.Grossjohann
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=m3k8x0c4ty.fsf@quimbies.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).