unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Mark Anderson <MarkR.Anderson@amd.com>
To: Carl Worth <cworth@cworth.org>,
	"notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Thoughts on not seeing messages I can't deal with (yet, or now, or here...)
Date: Fri, 26 Feb 2010 16:33:57 -0700	[thread overview]
Message-ID: <3wdy6if4lne.fsf@mhdcelk-nx01.amd.com> (raw)
In-Reply-To: <87zl2v4vjt.fsf@yoom.home.cworth.org>

Carl,

There's a post from a while ago about using GTD on Remember The Milk.

Remember the Milk as described here is mainly a todo manager, but the
saved search (as a list of todo tasks that match the criterion) is
what's being utilized here that makes me think so much of notmuch.

This seems to capture some of the things that you want to see, since you
are trying to manage action items which happen to live in mail bodies.

http://blog.rememberthemilk.com/2008/05/guest-post-advanced-gtd-with-remember-the-milk/

apparently another post has expired on the topic, with some focus on
contexts:

http://web.archive.org/web/20080331121051/http://www.geektronica.com/2007-01-15-gtd-with-rtm-getting-things-done-with-remember-the-milk

The main tool in use here is a viewport on the collection of things that
might need to be reviewed. RTM tabs (which are saved searches) which you
have designed to be the contexts you might be executing in, in this
case.

I know this is related pretty heavily to what you are looking for, but
how to bring this about specifically, that's going to be up to you.

Enjoy,
-Mark

On Fri, 26 Feb 2010 14:00:06 -0600, Carl Worth <cworth@cworth.org> wrote:
> [This mail started as some off-topic rambling in my reply to the
> notmuch-reply script. So that's why it starts on one topic and ends
> somewhere else entirely.]
> 
> I'm currently avoiding any locking failures with notmuch commands by
> running "notmuch new" manually, (rather than from a cron job). And it
> occurs to me that running "notmuch new" manually has a certain
> benefit---it allows me to bring in a chunk of mail, and then process all
> of that (either by replying, or setting aside to a particular project or
> "todo" tag, etc.) without getting distracted by other mail coming in.
> 
> It almost makes me want to just run "notmuch new" something like once
> per day.
> 
> But then, of course, there are times where there are important messages
> I need to get to quickly, or fast-moving threads where I need to reply
> several times throughout the day.
> 
> But I do have particular mailing lists that I don't want to read more
> than once a day, for instance. If I wait until I have about a days worth
> of mail in those lists, then I can deal with them very efficiently,
> (just scan all the subjects, read a thread or two and the "* -inbox" the
> rest). This gets a lot less efficient if I have to deal with those lists
> on a regular basis throughout the day, (particularly before we have
> support for "muted" threads).
> 
> So I'd like to be able to deal with important messages as they come in,
> but postpone bulk stuff.
> 
> But I also notice that there's a bad tendency I have if I try to do this
> postponing manually. Mail starts collecting in one of these bulk-list
> folders, and I start training myself to ignore the folder, then it gets
> huge, (which discourages me even more from looking at it, etc.). [*]
> 
> So I want better support from notmuch to tell me what things deserve my
> attention, so that I can avoid training myself to ignore things. I think
> what I want here is the ability to set a threshold on a particular
> folder based on number of messages or date. Something like: "Don't show
> me this folder at all until it has more than X messages or until the
> oldest message is at least Y hours old".
> 
> [*] A similar, (but more dangerous), problem occurs with manually
> postponing things into a "todo" folder. If I just added a bunch of
> things to my todo folder then I have a tendency to think, "I don't need
> to look at that---that's got a bunch of things I just decided to
> postpone". But then I forget that I put some things in there previously
> that really need my attention now.
> 
> I know that what I really want instead of "todo" is a way to express the
> reason I'm postponing a message. There's probably some resource I'm
> missing that I need before I can deal with it. Perhaps that's:
> 
>   * I can't decide on this until I'm with co-workers and can talk about
>     this.
> 
>   * I can't resolve this until I'm at the office with the right hardware
>     to test.
> 
>   * I need to remember to do something with this when I'm at home.
> 
>   * I need a nice block of "discretionary time" to be able to give this
>     topic the attention I want to.
> 
>   * I need to look at this message again on this Saturday.
> 
> So what I really want to do is to tag things based on those criteria,
> ("office", "magic-hardware", "home", "discretionary", "2010-02-27"),
> which I can at least do now.
> 
> But what I'm currently missing is a way for the folders based on these
> tags to only appear at the right times, (when the resource is
> available).
> 
> When the messages appear at the wrong times, it just trains me to ignore
> things, and that's when I start forgetting things and let things fall
> through.
> 
> No concrete proposal here, but just some musings on the kinds of issues
> I'd really like to be exploring with notmuch, (once we can get past all
> these little things like maildir flags, keybindings, failed HTML
> rendering, missing FCC support, etc. etc. etc.).
> 
> -Carl
Attachment: ATT00001 (application/pgp-signature)
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2010-02-26 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 20:00 Thoughts on not seeing messages I can't deal with (yet, or now, or here...) Carl Worth
2010-02-26 23:33 ` Mark Anderson [this message]
2010-03-01 11:12 ` Michal Sojka

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=3wdy6if4lne.fsf@mhdcelk-nx01.amd.com \
    --to=markr.anderson@amd.com \
    --cc=cworth@cworth.org \
    --cc=notmuch@notmuchmail.org \
    /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).