From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <bremner@unb.ca>, notmuch <notmuch@notmuchmail.org>
Subject: Re: output file argument to notmuch dump.
Date: Mon, 10 Oct 2011 09:41:47 -0700 [thread overview]
Message-ID: <87y5wsajec.fsf@washington.ligo-wa.caltech.edu> (raw)
In-Reply-To: <8739f2qhla.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
On Sun, 09 Oct 2011 13:01:53 -0300, David Bremner <bremner@unb.ca> wrote:
> Another option occured to me that is consistent at least with notmuch
> tag and notmuch show would be to support the following transitional
> syntaxes
>
> notmuch dump file
> notmuch dump file [--] search terms
> notmuch dump -- search terms
>
> the first two could then be deprecated, and eventually the syntax
>
> notmuch dump search terms
>
> could be enabled.
Hey, David. I think this is a fine approach, Go with the transitional
"--" separator for one release or so, with a deprecation warning, and
then move to the standard form in the release after that.
> the question of whether to support
>
> notmuch dump --file foo.txt
>
> or something like
>
> notmuch --stdout=foo.txt dump
>
> could be dealt with later.
I realize the later probably requires more work, since we would have to
replace all print calls with a new function, but I think it's the
cleaner and more elegant solution. There's no reason to have an output
redirection option for "dump"s and not for any of the other commands.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-10-11 1:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 0:20 output file argument to notmuch dump David Bremner
2011-10-07 0:37 ` Dmitry Kurochkin
2011-10-07 0:53 ` David Bremner
2011-10-07 1:43 ` Tom Prince
2011-10-07 1:14 ` Jameson Graef Rollins
2011-10-07 10:23 ` Jesse Rosenthal
2011-10-07 11:15 ` Tomi Ollila
2011-10-07 17:22 ` Jameson Graef Rollins
2011-10-10 7:32 ` Tomi Ollila
2011-10-09 16:01 ` David Bremner
2011-10-10 13:49 ` david
2011-10-10 13:49 ` [PATCH 1/6] test: update dump-restore to use redirection instead of filename args david
2011-10-10 13:49 ` [PATCH 2/6] test: add tests for command line arguments to notmuch-dump david
2011-10-10 13:49 ` [PATCH 3/6] notmuch-dump: update handling of file name argument david
2011-10-10 13:49 ` [PATCH 4/6] notmuch-dump: treat any remaining arguments after the filename as search terms david
2011-10-10 13:49 ` [PATCH 5/6] test: all dump-restore tests should be working now david
2011-10-10 13:49 ` [PATCH 6/6] notmuch-dump: deprecate use of output file argument david
2011-10-16 20:34 ` Thomas Schwinge
2011-10-16 23:25 ` Re: David Bremner
2011-10-10 13:59 ` output file argument to notmuch dump Tomi Ollila
2011-10-10 14:25 ` David Bremner
2011-10-10 16:41 ` Jameson Graef Rollins [this message]
2011-10-11 2:12 ` David Bremner
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=87y5wsajec.fsf@washington.ligo-wa.caltech.edu \
--to=jrollins@finestructure.net \
--cc=bremner@unb.ca \
--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).