On Mon, 10 Oct 2011 09:41:47 -0700, Jameson Graef Rollins wrote:
> >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
On Sun 09 Oct 2011 19:01, David Bremner writes:
> On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
>>
>> I'd like to add a search term argument to notmuch dump (see
>> id:"87wrcijn1w.fsf at zancas.localnet" and followup for context). The
>> "notmuch" way would be to have
>>
>>
On Mon, 10 Oct 2011 16:59:06 +0300, Tomi Ollila wrote:
>
> In this case there would be 2 transitional syntaxes. IMHO
>
> 'notmuch dump ' causes least transitional pain.
>
I don't understand what you mean here. Can you elaborate?
notmuch dump
is not a transitional syntax, but rather a
On Fri 07 Oct 2011 20:22, Jameson Graef Rollins
writes:
> On Fri, 07 Oct 2011 14:15:39 +0300, Tomi Ollila wrote:
>> The option 2, i.e. optional --write (or -o|--output) should be available;
>> someone may run notmuch without using environment that provides
>> redirections (or it is just plain
On Sun, 09 Oct 2011 13:01:53 -0300, David Bremner 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
>
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@unb.ca wrote:
I'd like to add a search term argument to notmuch dump (see
id:87wrcijn1w.fsf@zancas.localnet and followup for context). The
notmuch way would be to have
notmuch dump search-term
do the right thing
Another
On Fri 07 Oct 2011 20:22, Jameson Graef Rollins jroll...@finestructure.net
writes:
On Fri, 07 Oct 2011 14:15:39 +0300, Tomi Ollila tomi.oll...@iki.fi wrote:
The option 2, i.e. optional --write (or -o|--output) should be available;
someone may run notmuch without using environment that
On Mon, 10 Oct 2011 16:59:06 +0300, Tomi Ollila tomi.oll...@iki.fi wrote:
In this case there would be 2 transitional syntaxes. IMHO
'notmuch dump search-terms' causes least transitional pain.
I don't understand what you mean here. Can you elaborate?
notmuch dump search-terms
is not
On Sun, 09 Oct 2011 13:01:53 -0300, David Bremner brem...@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
On Mon, 10 Oct 2011 09:41:47 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
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
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
>
> I'd like to add a search term argument to notmuch dump (see
> id:"87wrcijn1w.fsf at zancas.localnet" and followup for context). The
> "notmuch" way would be to have
>
> notmuch dump
>
> do the right thing
Another option occured
On Fri 07 Oct 2011 13:23, Jesse Rosenthal writes:
> On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
>> 1) just delete the output file option from notmuch-dump, and use shell
>>redirection. So far I don't see a non-contrived example when writing
>>an output file directly is
On Fri, 07 Oct 2011 14:15:39 +0300, Tomi Ollila wrote:
> The option 2, i.e. optional --write (or -o|--output) should be available;
> someone may run notmuch without using environment that provides
> redirections (or it is just plain simpler to give the command line option
> instead of doing
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
> 1) just delete the output file option from notmuch-dump, and use shell
>redirection. So far I don't see a non-contrived example when writing
>an output file directly is useful, but maybe that is just a failure
>of imagination.
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
>
> I'd like to add a search term argument to notmuch dump (see
> id:"87wrcijn1w.fsf at zancas.localnet" and followup for context). The
> "notmuch" way would be to have
>
> notmuch dump
>
> do the right thing, and that is easy
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@unb.ca wrote:
1) just delete the output file option from notmuch-dump, and use shell
redirection. So far I don't see a non-contrived example when writing
an output file directly is useful, but maybe that is just a failure
of
On Fri 07 Oct 2011 13:23, Jesse Rosenthal jrosent...@jhu.edu writes:
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@unb.ca wrote:
1) just delete the output file option from notmuch-dump, and use shell
redirection. So far I don't see a non-contrived example when writing
an
On Fri, 07 Oct 2011 14:15:39 +0300, Tomi Ollila tomi.oll...@iki.fi wrote:
The option 2, i.e. optional --write (or -o|--output) should be available;
someone may run notmuch without using environment that provides
redirections (or it is just plain simpler to give the command line option
instead
On Fri, 07 Oct 2011 04:37:56 +0400, Dmitry Kurochkin wrote:
> On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner 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
On Thu, 06 Oct 2011 21:53:57 -0300, David Bremner wrote:
> On Fri, 07 Oct 2011 04:37:56 +0400, Dmitry Kurochkin gmail.com> wrote:
> > On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
>
> > IMHO 1[+2] is the way. It breaks the dump command interface, but would
> > make it consistent
I'd like to add a search term argument to notmuch dump (see
id:"87wrcijn1w.fsf at zancas.localnet" and followup for context). The
"notmuch" way would be to have
notmuch dump
do the right thing, and that is easy enough _except_ that
notmuch dump foo
writes the output to file foo.
I
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner wrote:
> I see several options.
>
> 1) just delete the output file option from notmuch-dump, and use shell
>redirection. So far I don't see a non-contrived example when writing
>an output file directly is useful, but maybe that is just a
I'd like to add a search term argument to notmuch dump (see
id:87wrcijn1w.fsf@zancas.localnet and followup for context). The
notmuch way would be to have
notmuch dump search-term
do the right thing, and that is easy enough _except_ that
notmuch dump foo
writes the output to file foo.
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@unb.ca wrote:
I'd like to add a search term argument to notmuch dump (see
id:87wrcijn1w.fsf@zancas.localnet and followup for context). The
notmuch way would be to have
notmuch dump search-term
do the right thing, and that is
On Fri, 07 Oct 2011 04:37:56 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@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
On Thu, 06 Oct 2011 21:20:40 -0300, David Bremner brem...@unb.ca wrote:
I see several options.
1) just delete the output file option from notmuch-dump, and use shell
redirection. So far I don't see a non-contrived example when writing
an output file directly is useful, but maybe that
26 matches
Mail list logo
