From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] now in next: sup-cmd
Date: Thu, 04 Mar 2010 02:48:16 -0500 [thread overview]
Message-ID: <1267687531-sup-5689@zyrg.net> (raw)
I already had the code for a sup-server sup-cmd sitting around, so I
wrote a small compatibility layer that lets it run using the mainline
index API. It outputs YAML.
Usage:
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
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-03-04 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 7:48 Rich Lane [this message]
2010-03-04 13:10 ` Nicolas Pouillard
2010-03-04 18:25 ` Carl Worth
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=1267687531-sup-5689@zyrg.net \
--to=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