Re: Movement ops

["Jody M. Klymak" <jklymak@apl.washington.edu>]

Hi Kai

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
    KG> The keys are still bound to the same functions, but the
    KG> behavior of those functions changes.  In particular,
    KG> *-unread-* is a bit of a misnomer when
    KG> gnus-summary-goto-unread is `never' 8-)

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 get back to your original question, if you make
gnus-summary-next-unread-article exactly the same as
gnus-summary-next-article then you're kind of hosed for coming up with a
keybinding to go to the next unread article since you have no function
that performs that function any more (unless there is a
gnus-summary-next-unread-article-really-really-I-mean-it-this-time
function you can bind to)

It sounds like if you want E to go to the next article rather than the
next unread you need to change whatever E is bound to.

Cheers,  Jody

-- 
Jody Klymak                         APL/School of Oceanography,
Doctoral Candidate                  University of Washington
mailto:jklymak@apl.washington.edu   (206)-685-9080
http://www.ocean.washington.edu/people/grads/jklymak/