Re: Collapsing Threads
On Sat, May 19, at 07:18 Danny wrote:
> Here is my folder-hooks file,
>
> # - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> #
> # Change settings based on mailbox
> #
> # folder-hook [!]<pattern> <command>
> #
> # <command> is executed when opening a mailbox matching <pattern>
> #folder-hook `exho =incoming/archived/*` `color index white default`
> #folder-hook . 'set sort=date-sent'
> #folder-hook mutt 'set hdr_format="%4C %Z %02m/%02N %-20.20F (%4l) %s"'
> #folder-hook =mutt my_hdr Revolution: \#9 # real comment
> #folder-hook . 'set reply_regexp="^re:[ \t]*"'
>
> # this mailing list prepends "[WM]" to all non reply subjects, so set
> # $reply_regexp to ignore it
> #folder-hook +wmaker 'set reply_regexp="^(re:[ \t]*)?\[WM\][ \t]*"'
>
Thanks,
At first, there is no reason to source the file, since it's commented.
Second, you have to understand that there is _something_ in your
configurations files that change the *default* mutt's behavior, which is
not collapsed threads in any way; unless there is a bug, which I am
pretty sure there isn't.
For instance, I do have these lines in my muttrc, which they both (the
binding and the hook) change the default mutt's behavior, which in the
our case is expanded threads.
bind index z limit
folder-hook . 'push z~d<3d<enter><collapse-all>'
Now since you started mutt in debug mode, and you didn't noticed any
suspicious as you said, then the only other option is something in your
configuration files. Hint: grep for collapse.
There is no mystery or black magic in the software world, everything is
predictable, unlike the fragile and capricious human mind.