Re: Movement ops

[Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)]

"Jody M. Klymak" <jklymak@apl.washington.edu> writes:

> Hmmm, whats the point of that?  It seems that if you have a
> gnus-summary-next-unread-article and a gnus-summary-next-article then
> you have all the functionality you could want.  Then perhaps you set a
> switch in whatever "E" is bound to to use one or the other.  

To make this clear: I was describing the current Gnus behavior.  I
think the current Gnus behavior is not, uh, orthogonal enough.  There
should be a way to mark a message as expirable without moving at all,
with moving to the prev/next msg, with moving to the prev/next unread
msg.  Alas, there's only gnus-summary-mark-as-expirable which moves
depending on gnus-summary-goto-unread.

Providing all the commands is not difficult to do at all, but thinking
up a meaningful set of key bindings and/or a way for users to
customize the key bindings is nontrivial, I think.  Maybe the first
that should be decided is whether one wants to stay backward
compatible or not.

kai
-- 
A preposition is not a good thing to end a sentence with.