From: Carl Worth <cworth@cworth.org>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>,
Rich Lane <rlane@club.cc.cmu.edu>,
sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] now in next: sup-cmd
Date: Thu, 04 Mar 2010 10:25:06 -0800 [thread overview]
Message-ID: <87bpf4eygt.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <4b8fb14f.0702d00a.5427.ffffe469@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]
On Thu, 04 Mar 2010 05:10:39 -0800 (PST), Nicolas Pouillard <nicolas.pouillard@gmail.com> wrote:
> > sup-cmd count 'is:inbox'
> > sup-cmd query --offset 10 --limit 5 'is:unread'
> > sup-cmd label --add-labels 'bugs' --remove-labels 'inbox' 'is:inbox AND from:bugzilla'
> > sup-cmd add --labels 'sent' < email
>
> This is great!
>
> BTW is there any hope to reach a kind of concensus of a nice CLI API with
> notmuch people?
It seems to me, at least, like that would be a worthwhile effort.
I still consider the notmuch UI young enough that it's still quite
flexible. And I'm here on the sup list if we want to talk here.
For reference, the rough equivalent of the above commands in notmuch
would be (with footnotes where things don't match exactly):
notmuch count 'tag:inbox'
notmuch search 'tag:unread' [*]
notmuch tag +bugs -inbox 'tag:inbox AND from:bugzilla'
notmuch new [**]
So, I obviously switched from "label" to "tag" when I moved from sup to
notmuch. But I do like the "is:" prefix---I can easily see adding that
at least.
-Carl
[*] Notmuch currently doesn't have an equivalent of --offset and --limit
but did have --first and --max-threads for a while, (and we'll probably
be adding the same feature back again). The names of "offset" and "limit"
sound good to me.
[**] "notmuch new" is certainly only a very poor approximation of
"sup-cmd add". The notmuch cli does not currently have any way to add an
explicit file, (instead, "notmuch new" simply finds all new, renamed,
and deleted files within the mail store). By the way, what's the
semantic for "sup-cmd add" when it accepts a message on stdin? How is
the message content every returned later?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-03-04 18:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 7:48 Rich Lane
2010-03-04 13:10 ` Nicolas Pouillard
2010-03-04 18:25 ` Carl Worth [this message]
2010-03-05 8:40 ` Nicolas Pouillard
2010-03-10 0:08 ` Carl Worth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bpf4eygt.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=nicolas.pouillard@gmail.com \
--cc=rlane@club.cc.cmu.edu \
--cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox