From: David A Benjamin <davidben@MIT.EDU>
To: Ben Gamari <bgamari.foss@gmail.com>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: Notmuch command interface
Date: Thu, 11 Mar 2010 17:52:34 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.1.10.1003111748020.9755@dr-wily.mit.edu> (raw)
In-Reply-To: <4b990b7b.0e67f10a.073c.0686@mx.google.com>
On Thu, 11 Mar 2010, Ben Gamari wrote:
> While the notmuch command-line interface is fantastic, there defintely are a few
> gaps which hurt performance. Since I've been following, I've seen several
> threads on how to handle message addition and initial tagging[1][2]. I recall
> that some time ago Carl had the idea of applying only a 'new' tag during notmuch
> new. I strongly supported this proposal yet it seems that nothing ever became of
> it. Is there a reason for this? Would a patch be accepted?
>
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".
David
next prev parent reply other threads:[~2010-03-11 22:52 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 [this message]
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 ` Notmuch command interface Sebastian Spaeth
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=alpine.DEB.1.10.1003111748020.9755@dr-wily.mit.edu \
--to=davidben@mit.edu \
--cc=bgamari.foss@gmail.com \
--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).