On 14Apr2016 18:15, Francesco Ariis <[email protected]> wrote:
On Thu, Apr 14, 2016 at 05:47:48PM +0200, Andreas Doll wrote:
I'm using mutt in conjunction with offlineimap to filter mailinglists into
separate folders. Usually I decide quickly if I'm interested in a thread or
not - if not I press Ctrl-r to mark this thread as read and move on.
The "problem" with this is, that subsequent replies to this thread will marked
as new again. Is there a way (flagging?) such that subsequent replies to this
thread will be marked also as read, maybe utilizing offlineimap (which is able
to mark mails as read)?
Hey Andreas,
I wrote a small folder-hook pattern which accomplishes a similar task
(deletes instead 'mark as read') [1]. I suspect it can be modified to
suit your needs (tag-pattern + tag-prefix maybe?).
Fire again if you need help
[1] http://ariis.it/static/articles/mutt-ml/page.html
TL;DR: Francesco' pattern is:
~l~N(!~(!~x.+))(!~(~F))
which matches list messages where the whole thread is (N)ew, where no message
in the thread lacks a Reply-To: or References, where no message in the thread
is (F)lagged. Ergo, list message replies to threads whose starting message has
been removed (as uninteresting).
That is very clever!
(BTW, the ~x pattern only needs to be present, not match the whole line, so you
can use "~x." instead of "~x.+".)
I'm about to adopt that here with small tweaks based on my own
behaviour/desires:
I am dropping the ~l, I do not use the list mutt settings.
I am going to require matching threads to have no Subject lines which do not
commence with "^(\[[^]]*\] *)?Re:" (subjects starting with "Re:", allow for
list subject tags like "[spinx-users]"; some brief tests in my python folder
found some shiny new subjects like this:
blah (was: blah-old)
and of course rampant thread hijacking by naive users. I am prepared to
consider them "new threads", at least wanting reexamination.
So I'm testing with this at present:
macro index <Esc>l '<limit>~N(!~(!~x.))(!~(~F))(!~(!~s"(\\[[^]]*\]
*)?[Rr][Ee]:"))' 'tag unflagged all-new replies to deleted threads'
and it definitely seems to be showing only boring stuff. I may combine it with
~= (duplicate message id - multiple delivery of the same message) and consider
it a tidy-this-folder tool. And eventually run it by default on folder entry,
maybe.
I can see I will need to teach myself to ^R (mark whole thread read) instead of
^D (delete/archive whole thread) for discussions I _do_ intend to follow.
Fortunately I already bind ^R to:
<read-thread><collapse-thread><next-unread>
which folds such things away quietly for me.
Thank you Francesco!
Cheers,
Cameron Simpson <[email protected]>
