On 06Jan2014 00:50, Kim Christensen <[email protected]> wrote:
> Is there a setting or magic trick for automatically collapsing
> threads? I cannot seem to find anything that would affect the initial
> thread collapse/uncollapse state (e.g. upon entering a mailbox).
My mutt state is arranged so that completely read threads are
collapsed, and threads with unread items are expanded.
My muttrc has:
set collapse_unread=no
set uncollapse_jump=yes
folder-hook . 'push "<collapse-all>"'
folder-hook . 'push ":set collapse_unread=no<enter>"'
macro index \R "<read-thread><collapse-thread><next-unread>" "mark the
current thread as read"
macro index '{' ':set my_oldcollapse_unread=$collapse_unread<enter>:set
collapse_unread=yes<enter><collapse-thread>:set
collapse_unread=$my_oldcollapse_unread<enter>' 'Collapse thread.'
macro index '}' "{" '(Un)collapse thread.'
Specificly, the folder-hooks push a <collapse-all> command, collapsing
all threads when I first enter a mail folder. Depending what you
want, you may be able to push various commands on folder entry to
achieve the state you want.
I've also included a few keyboard macros I find useful.
\R mark whole thread as read and collapse it
{ Collapse the current thread.
} Uncollapse the current thread (really a toggle, but I _use_ it for
uncollapse).
Hope this helps,
--
Cameron Simpson <[email protected]>
It looks like you've got Mister Bus Error installed. - tjc
