From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus-summary-mark-as-expirable
Date: 07 Nov 1999 14:48:29 +0100 [thread overview]
Message-ID: <vaf66zeza36.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Karl EICHWALDER's message of "07 Nov 1999 11:06:55 +0100"
Karl EICHWALDER <ke@gnu.franken.de> writes:
> [...] gnus-summary-mark-as-expirable should not move to
> unread/unticked article. Instead it should move next article; it
> shouldn't not care whether this article is read or unread. [...]
Because of this, I have set gnus-summary-goto-unread to `never'.
But I still think that it should be possible to make marking and
moving orthogonal, ie for every mark there should be a command that
goes to the next article, a command that goes to the next unread
(unmarked?) article, the two analogous commands for previous messages,
and a command that doesn't move at all.
Once we have these commands, some clever scheme could be designed for
choosing key bindings.
kai
--
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser
prev parent reply other threads:[~1999-11-07 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-07 10:06 gnus-summary-mark-as-expirable Karl EICHWALDER
1999-11-07 13:48 ` Kai Großjohann [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=vaf66zeza36.fsf@lucy.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).