From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Feature Req: Command line search/display options
Date: Fri, 26 Oct 2007 20:46:58 -0700 [thread overview]
Message-ID: <1193456434-sup-4612@south> (raw)
In-Reply-To: <471361DE.9040008@quintic.co.uk>
Excerpts from Marcus Williams's message of Mon Oct 15 05:49:34 -0700 2007:
> 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.
In SVN there's a devel/console.sh, which shows how to hook into Sup
without invoking the interface. Here are some examples:
> sup --search "some search term"
$ sh devel/console.sh
[Fri Oct 26 20:37:55 -0700 2007] loading index...
[Fri Oct 26 20:37:55 -0700 2007] loaded index of 63434 messages
>> Index.index.search_each("potato") { |id, score| m = Index.build_message(id); puts "[#{id}] [#{m.from}] [#{m.subj}]" }
[65155] [William Morgan <wmorgan at masanjin.net>] [potato]
[20758] [Sam Smoot <ssmoot at gmail.com>] [Declaring instance variables dynamically]
[6048] [David Balmain <dbalmain.ml at gmail.com>] [[Ferret-talk] hello, acts_as_ferret questions, any help greatly appreciate]
[6047] [koloa <none at none.com>] [[Ferret-talk] hello, acts_as_ferret questions, any help greatly appreciate]
[2251] [William Morgan <wmorgan at masanjin.net>] [lunch today]
> sup --display someid0
>> puts Index.build_message(6047).raw_message
From ferret-talk-bounces at rubyforge.org Mon Oct 09 08:17:37 2006
[...]
You can submit a patch that adds --search and --display options to
bin/sup, if you like.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-10-27 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 12:49 Marcus Williams
2007-10-15 17:41 ` Christopher Warrington
2007-10-27 3:46 ` William Morgan [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193456434-sup-4612@south \
--to=wmorgan-sup@masanjin.net \
/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