unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: Notmuch command interface
Date: Fri, 12 Mar 2010 10:18:32 +0100	[thread overview]
Message-ID: <87eijpucd3.fsf@SSpaeth.de> (raw)
In-Reply-To: <alpine.DEB.1.10.1003111748020.9755@dr-wily.mit.edu>

> To avoid breaking the current behavior, what if the set of tags applied to 
> new/moved/deleted(?) messages could be set on the command line or some 
> other library interface, while just perhaps defaulting to unread/inbox? 
> This would support both the current behavior and a hooks-like workflow 
> without notmuch itself treating any tags (new, unread, inbox, etc.) as 
> "special".

+1. For some, the default "inbox unread" might just be the correct
thing, while others may want "new". I know that I don't need any special
tag for new mails, as I applied the "sync maildir flags" patch. So
configurable in .notmuch-config with a default of "inbox unread" to keep
behavior consistent seems the best way to me.

Sebastian

      parent reply	other threads:[~2010-03-12  9:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 15:25 Notmuch command interface Ben Gamari
2010-03-11 22:52 ` David A Benjamin
2010-03-12  0:52   ` Ben Gamari
2010-03-12  8:31   ` Michal Sojka
2010-03-12 14:46     ` Sebastian Spaeth
2010-03-12 15:03       ` Michal Sojka
2010-03-12 16:03         ` Sebastian Spaeth
2010-03-14 18:15           ` Michal Sojka
2010-03-14 18:19             ` [PATCH] Produce valid JSON output even if mail body is empty Michal Sojka
2010-03-14 19:01               ` James Westby
2010-03-14 20:44                 ` [PATCH] Fix invalid JSON output for NULL strings Michal Sojka
2010-03-12  9:18   ` Sebastian Spaeth [this message]

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=87eijpucd3.fsf@SSpaeth.de \
    --to=sebastian@sspaeth.de \
    --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).