From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] Feature Req: Command line search/display options
Date: Mon, 15 Oct 2007 13:49:34 +0100 [thread overview]
Message-ID: <471361DE.9040008@quintic.co.uk> (raw)
Hi -
I posted this in the tracker on RubyForge but then noticed the mail list
so I thought I'd put it here for discussion. I'd like to add some
command line options to search/display messages, because then I can
script using sup outside of sup as it were.
So c&p from tracker:
-------------------------
What would be _really_ nice (and I might have a go at a patch if given
some pointers where to start looking) would besome command line options
to search for messages (printing a list of matches and exiting) and to
display a single message (and exit).
What I'm thinking is something like:
sup --search "some search term"
[someid0] [from] [Subject...................]
[someid1] [from] [Subject...................]
[someid2] [from] [Subject...................]
[someid3] [from] [Subject...................]
[someid.] [from] [Subject...................]
[someidn] [from] [Subject...................]
sup --display someid0
From: blah@blah.com
Subject: This is my subject
The body.
-------------------------
Like I said, I can implement this and submit a patch but it might be
faster if someone pointed me to some relevant places in the source (or
told me it can already be done....)
I'd also quite like the output to be machine parsable as an option (in
the case of the search results anyway) and be able to add/remove labels
from messages/threads, but I thought I'd start with plain text :)
Anyone else find this useful?
Marcus
next reply other threads:[~2007-10-15 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:49 Marcus Williams [this message]
2007-10-15 17:41 ` Christopher Warrington
2007-10-27 3:46 ` William Morgan
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=471361DE.9040008@quintic.co.uk \
--to=marcus-sup@quintic.co.uk \
/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