On 29Mar2019 18:21, Erik Christiansen <dva...@internode.on.net> wrote:
On 28.03.19 13:24, Max Görner wrote:
I am a very pleased Mutt user for several years now. However, I would
love to
have a threading similar to GMail, showing send and received messages in the
same thread.
I wonder whether one could just configure mutt such as to save all send
messages to Inbox again. Of course, that would clutter the inbox severely, but
a) I have a hook limiting the view to ~(~N|~F) already
b) the cluttering might be counteracted by Mutt's threading capabilities.
Display filtering of one enormous clutter had never occurred to me as a
viable option.
I do the following to reduce clutter:
I sort folders threaded reverse (new stuff on top).
And I push these commands on entry to a folder:
# mark stuff I posted as read
folder-hook . 'push ":set
auto_tag=no<enter><untag-pattern>~T<enter><tag-pattern>~P~N<enter><tag-prefix-cond><clear-flag>N<untag-pattern>~T<enter><end-cond>:set
auto_tag=yes<enter>"'
# collapse read threads
folder-hook . 'push "<collapse-all>"'
folder-hook . 'push ":set collapse_unread=no<enter>"'
To explain:
First I mark anything new which I wrote (~P~N) as "read" - after all,
I've seen it. This catches stuff from me via lists and anything I've run
through my filing rules (email I sent gets filed like other email in my
regime).
Then I issue a <collapse-all> to collapse _all_ threads to a single line
each. And then issue ":set collapse_unread=no<enter>" to uncollapse
threads with new messages.
Between the collapsing and the thread sort, new threads with unread
messages are at the top of my email view.
Aside: I sort new-to-top, the reverse of the default, because I like to
see the whole thread before replying. I found sorting conventionally got
me involved before I'd seen followon posts saying the same stuff I was
saying.
There are various incoming mail filtering tools in any
linux distro repository - the one I've used for decades is procmail.
I've set it to stream incoming mail to a separate inbox for each mailing
list, one for family, and the rest remain in /var/spool/mail/erik.
On list mailboxes, record is just set to "sent", as the list server
provides a copy of my mail for threading. A couple of hooks, folder and
recipient, record to =family when required. So, yes, posts & replies
thread nicely.
I set $record to my "+spool-out" folder, which is monitored and cross
files messages (like you, family to one box and so on). As you might
imagine, inbound email lands in "+spool-in" which is also monitored and
filed from there; that folder is post my crude prefilter for spam.
To further reduce clutter, and highly optimise searches, I delete 95 -
99% of all list mail,
My mutt "delete" keystrokes move the messages to parallel "archive"
folders: "+mail" to "+O/mail", and "O" is a symlink to a per year
directory which I flip each January. So I get "+OLD/2018/mail" etc,
purely to control file size.
and archive any pearls in topic-specific secondary
mailboxes; there are 70 for mutt, 456 for LinuxCNC, and 1259 mailboxes
in all. (When looking for a hint on vim scripting a few minutes ago, for
a reply on another list, I only had to consider the subject lines of 205
posts in the mailbox vim_script, rather than who knows how many in the
104 vim mailboxes, let alone the umpty thousands if there were only one
inbox. (I'm still amazed at the thought.)
I use notmuch to search email; I have a couple of handle shell scripts
9with short names) to do lookups. Saving deciding _where_ to look -
notmuch looks everywhere and one just has to type an ok search. Then it
opens the results in mutt anyway for easy persual (the (l)imit keystroke
is a grwat boon here).
My "inbox" is supposed to be my "priority" categories: personal email,
family, banking. And unfortunately, nearly a bazillion other special
criteria. Still, lists email goes to its own folder.
I group lists by topic. Several "python" lists land in "+python", mutt
and other mail tech related lists in "+mail" and so forth.
Cheers,
Cameron Simpson <c...@cskk.id.au>
