unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Darren McGuicken <mailing-notmuch@fernseed.info>
To: Matthieu Lemerre <racin@free.fr>, notmuch@notmuchmail.org
Subject: Re: [PATCH] How to improve the mail handling workflow?
Date: Fri, 12 Nov 2010 16:58:02 +0000	[thread overview]
Message-ID: <87pquafpid.fsf@bookbinder.fernseed.info> (raw)
In-Reply-To: <87d3qa5wl1.fsf@free.fr>

[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]

On Fri, 12 Nov 2010 17:35:22 +0100, Matthieu Lemerre <racin@free.fr> wrote:
> I prefer to add tags, for the following reasons:

It sounds like we do much the same things with our mail except that your
approach is quite disciplined and mine quite lazy :-)

>  - If I want to search through a mailing list, I don't have to
>  remember its address. Saved searchs solve the problem only partly,
>  because I am not able to make complex queries involving several saved
>  searches. This could be solved only by making notmuch aware of saved
>  searches.

[...]

> By default, hitting the space bar throughout a thread would remove
> every tag from the thread, so you keep asking "where was the mail in
> my inbox that I have read and I can't find anymore?"

As it's so quick, I tend to search my entire archive, even for new
messages, through progressive stages of filtering (which is really all
that a saved search is) starting off knowing only vaguely what it is
that I'm looking for.

For instance 'there was something on the notmuch list about printing
format issues recently' would be 's to:notmuch' 'f print' 'f format' etc
until I see what I'm looking for (or something similar) in the results.
That particular set of steps gives me a buffer with 24 threads in it,
the second of which is what I was looking for.  I tend not to even
bother with subject header based searches unless I know for sure that
what I'm looking for had an unusual subject.

It sounds like a lot of work when I write it out long-form, but it's
incredibly intuitive and so far always gets me what I need.

I can see your approach has its own merits though.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2010-11-12 16:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 15:23 [PATCH] How to improve the mail handling workflow? Matthieu Lemerre
2010-11-12 15:33 ` Jameson Rollins
2010-11-12 16:39   ` Matthieu Lemerre
2010-11-14 21:07   ` Sebastian Spaeth
2010-11-14 21:19     ` Jameson Rollins
2010-11-14 21:31     ` Sebastian Spaeth
2010-11-15  8:28     ` David Edmondson
2010-11-12 15:39 ` Darren McGuicken
2010-11-12 16:35   ` Matthieu Lemerre
2010-11-12 16:58     ` Darren McGuicken [this message]
2010-11-14 21:34     ` Sebastian Spaeth
2010-11-14 23:25       ` Matthieu Lemerre
2010-11-13  6:05   ` Michal Sojka
2010-11-13 11:03     ` Darren McGuicken
2010-11-15  8:00       ` Michal Sojka
2010-11-12 17:05 ` David Edmondson
2010-11-12 17:48   ` Matthieu Lemerre
2010-11-12 17:42     ` David Edmondson
2010-11-13 16:43 ` Cédric Cabessa
2010-11-13 18:41   ` Jameson Rollins
2010-11-14 17:01     ` Matthieu Lemerre
2010-11-14 19:13       ` Jameson Rollins
2010-11-14 21:43         ` Matthieu Lemerre
2010-11-14 21:45 ` Michael Hudson

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=87pquafpid.fsf@bookbinder.fernseed.info \
    --to=mailing-notmuch@fernseed.info \
    --cc=notmuch@notmuchmail.org \
    --cc=racin@free.fr \
    /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).