On Tue, 23 Nov 2010 18:09:03 -0800, Carl Worth cwo...@cworth.org wrote:
Meanwhile, while adding the --output= test, I noticed some inconsistency
in the output:
$ notmuch search --output=messages ... | head -1
id:1272355278.3878.111.camel@thor.local
The inconsistency is the
On Wed, 24 Nov 2010 11:40:46 -0800, Carl Worth cwo...@cworth.org wrote:
So my inclination is to remove the prefixes and then recommend that you
do:
notmuch search --output=threads | sed -e 's/^/thread:'
in your script.
Hey, Carl. I think that's reasonable.
jamie.
On Tue, 23 Nov 2010 18:09:03 -0800, Carl Worth wrote:
The inconsistency is the presence of the thread: and id: prefixes in
the first two cases, (note that there isn't any tag: prefix in the
last case). I can't find any good justification for these.
I use the output of notmuch search
On Wed, 24 Nov 2010, Carl Worth wrote:
Michal, in trying to add a test for that bug, I found that the current
test suite infrastructure can't catch it because the shell's $()
construct doesn't distinguish whether that final newline is present or
not. I don't see an easy way to fix this, (other
On Wed, 24 Nov 2010 09:38:46 +0100, Sebastian Spaeth sebast...@sspaeth.de
wrote:
On Tue, 23 Nov 2010 18:09:03 -0800, Carl Worth wrote:
The inconsistency is the presence of the thread: and id: prefixes in
the first two cases, (note that there isn't any tag: prefix in the
last case). I can't
I just committed a bug fix for the missing final newline from notmuch
search --output=tags. I don't recall who reported the bug, but thanks!
Michal, in trying to add a test for that bug, I found that the current
test suite infrastructure can't catch it because the shell's $()
construct doesn't
On Tue, 23 Nov 2010 18:09:03 -0800, Carl Worth cwo...@cworth.org wrote:
I think the right answer is to drop those prefixes in the output. Does
anybody disagree? Does anyone have any scripts that are already
consuming the output of notmuch search --output=threads or notmuch
search
