On Thu, Feb 16, 2012 at 17:02:19 -0500, Patrick Shanahan wrote:
> * Christian Dysthe <cdys...@gmail.com> [02-16-12 16:08]:
> > 
> > 
> > On 02/16/12 at 05:21pm, Maurice McCarthy wrote:
> > > Hitting Tab already does this for me.
> > 
> > Not for me.  Tab just jumps from one unread message to the next. I have
> > to hit space to scroll down the message, but it then goes to the next
> > message, not the next unread. 
> 
> You undoubtedly have something changing that action in your /etc/muttrc or
> ~/.muttrc.  To eliminate the actions from the config files, try using mutt
> from the cl:
>   mutt -F /dev/null
> 
> and see if the actions return to those expected, ie:
>    TAB = next new/unread
>    SPACE = next page
> 

I don't believe Maurice's behavior is different than the default...

He's talking about what happens when he runs the "next-page" function
(bound to the SPACE key) while viewing the last screen of the current
message, which currently advances to the next message (as controlled by
the setting of the pager-stop variable -- presumably that's set to the
default value of "no").

What Maurice is asking is if there's any way to get this "move to next
message" operation of the next-page function to instead be "move to next
_new_ message"....

(In other words, he's not saying that TAB doesn't have the default
behavior of going to the the next new message, but rather that it
doesn't have the effect of paging down though his current message the
way the SPACE key does, which is what he's looking for....)


Maurice, I don't know of a direct way to do what you want, but one thing
you could try is to do a "limit" to new messages only (~N) when you
start reading your mail.  That way, the "next message in index" that
next-page advances to would in fact jump to the next new message....

(But you would have to refresh the limit periodically as you read your
messages to remove the ones you've just read from the current index, and
of course remove the limit when you wanted to go back an look at
previously-read messages.)

                                                        Nathan



Reply via email to