From: Tom Prince <tom.prince@ualberta.net>
To: David Bremner <bremner@unb.ca>,
Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: output file argument to notmuch dump.
Date: Thu, 06 Oct 2011 21:43:38 -0400 [thread overview]
Message-ID: <871uup8tkl.fsf@hermes.hocat.ca> (raw)
In-Reply-To: <87sjn539lm.fsf@zancas.localnet>
On Thu, 06 Oct 2011 21:53:57 -0300, David Bremner <bremner@unb.ca> wrote:
> On Fri, 07 Oct 2011 04:37:56 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
> > On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner <bremner@unb.ca> wrote:
>
> > IMHO 1[+2] is the way. It breaks the dump command interface, but would
> > make it consistent with other commands. Implementing the second option
> > (for all commands) is nice but independent and optional. Also, perhaps
> > --output, --output-file or smth would a better name than --write.
>
> I'm not fussy about the name, except that --output is taken, and I
> thought there might be some benefit of making options have unique
> prefixes.
Is -o/--output taken before the subcommand? i.e.
notmuch -o <dumpfile> dump <query> <terms>
Or would that be to confusing?
(-o is fairly standard for stdout redirection, so it would be nice to
use that for notmuch, as well.)
Tom
next prev parent reply other threads:[~2011-10-07 1:43 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 [this message]
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
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=871uup8tkl.fsf@hermes.hocat.ca \
--to=tom.prince@ualberta.net \
--cc=bremner@unb.ca \
--cc=dmitry.kurochkin@gmail.com \
--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).