From: Sean Whitton <spwhitton@spwhitton.name>
To: Reto <reto@labrat.space>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch and mailing lists
Date: Sun, 03 May 2020 08:50:49 -0700 [thread overview]
Message-ID: <87k11thvae.fsf@athena.silentflame.com> (raw)
In-Reply-To: <20200502131358.ciph4tv5dmzqdy54@feather.localdomain>
Hello Reto,
On Sat 02 May 2020 at 03:13pm +02, Reto wrote:
> On Fri, May 01, 2020 at 12:30:28PM -0700, Sean Whitton wrote:
>> I've not yet used NNTP to read mailing lists myself, but I think there
>> are limitations to the way I currently read lists
>
> What are you missing exactly?
> If we know what your actual problems are there might be better solutions forthcoming.
Well, I would like to be able to handle a higher volume of messages
faster. I think that I am typically reluctant to subscribe to new lists
because I know that I'm not efficient at processing the mail.
People who use NNTP to read mailing lists talk about the following sorts
of things which speed things up:
- efficient killfiles/filters
- manually killing subthreads
- expiration/catching up
- browsing lists without going through the process of subscription
and/or downloading archives
I'd be interested to hear what techniques people have for making notmuch
capable of getting through mailing list mail faster. I find that
notmuch is great for practising Inbox Zero on personal mail, and for
searching to find old mail, but I haven't made it especially good for
dealing with discussion forums yet.
I've come up with a few ideas myself in the past few days but they're
fairly simple.
--
Sean Whitton
next prev parent reply other threads:[~2020-05-03 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 19:30 notmuch and mailing lists Sean Whitton
2020-05-02 13:13 ` Reto
2020-05-03 15:50 ` Sean Whitton [this message]
2020-05-02 20:52 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k11thvae.fsf@athena.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=notmuch@notmuchmail.org \
--cc=reto@labrat.space \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).