notmuch with the bbdb

heyho. in the documentation it said, bbdb would work really well with message mode. my problem now is, that it is stated nowhere how to feed the database of notmuch to the bbdb initially. is there a way to export all the mail addresses in the maildirs to plaintext files? bbdb-snarf gives a prett

[PATCH 1/3] test: add basic show, search --format=text tests

Series LGTM, though I'm curious why you want the reply-to header, given that nothing I'm aware of consumes it. I second Jameson's opinion that we should push this first patch even if we wind up not pushing the others. Quoth Peter Wang on Jun 24 at 1:27 pm: > There didn't seem to be these basic t

Re: [PATCH 2/3] show: output Reply-To headers

On Tue, Jul 03 2012, Peter Wang wrote: > I want to see what the sender intended, before hitting reply. Given that there have been requests to see a lot of other headers as well, we probably need to have a discussion about which ones are worth of emitting, and how we give the user some more genera

[PATCH 2/3] show: output Reply-To headers

otmuch/attachments/20120703/f885e5c1/attachment.pgp>

Re: [PATCH 1/3] test: add basic show, search --format=text tests

Series LGTM, though I'm curious why you want the reply-to header, given that nothing I'm aware of consumes it. I second Jameson's opinion that we should push this first patch even if we wind up not pushing the others. Quoth Peter Wang on Jun 24 at 1:27 pm: > There didn't seem to be these basic t

Re: [PATCH 2/3] show: output Reply-To headers

On Tue, 03 Jul 2012 18:27:23 -0700, Jameson Graef Rollins wrote: > On Sat, Jun 23 2012, Peter Wang wrote: > > Output Reply-To headers when present in a message. > > These were missing in text and json output formats. > > I don't see why the Reply-To header is needed, given that we are > constru

Re: [PATCH 2/3] show: output Reply-To headers

On Sat, Jun 23 2012, Peter Wang wrote: > Output Reply-To headers when present in a message. > These were missing in text and json output formats. I don't see why the Reply-To header is needed, given that we are constructing reply templates, but I guess if someone thinks it's needed I don't see mu

[PATCH 2/3] show: output Reply-To headers

uchmail.org/pipermail/notmuch/attachments/20120703/de7a441d/attachment.pgp>

Re: [PATCH 1/3] test: add basic show, search --format=text tests

On Sat, Jun 23 2012, Peter Wang wrote: > There didn't seem to be these basic tests for --format=text, > as there are for --format=json. These are just the tests from > the `json' script, with adjusted expected outputs. As long as we're going to support this silly output format we should probably

[PATCH 1/3] test: add basic show, search --format=text tests

ytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120703/152623f1/attachment.pgp>

[PATCH 8/8] emacs: Switch from text to JSON format for search results

The JSON format eliminates the complex escaping issues that have plagued the text search format. This uses the incremental JSON parser so that, like the text parser, it can output search results incrementally. This slows down the parser by about ~4X, but puts us in a good position to optimize eit

[PATCH 7/8] emacs: Implement an incremental JSON parser

This parser is designed to read streaming JSON whose structure is known to the caller. Like a typical JSON parsing interface, it provides a function to read a complete JSON value from the input. However, it extends this with an additional function that requires the next value in the input to be a

[PATCH 6/8] test: New test for incremental search output parsing

This advises the search process filter to make it process one character at a time in order to test the pessimal case for incremental search output parsing. The text parser fails this test because it gets tricked into thinking a parenthetical remark in a subject is the tag list. --- test/emacs

[PATCH 5/8] emacs: Pass plist to `notmuch-search-show-result'

Rather than passing lots of arguments and then further passing those to `notmuch-search-insert-field', pass a plist containing all of the search result information. This plist is compatible JSON format search results. --- emacs/notmuch.el | 65 +++

[PATCH 4/8] emacs: Helper for reporting search parsing errors

This removes the last bit of direct output from the parsing function. With the parser now responsible solely for parsing, we can swap it out for another parser. --- emacs/notmuch.el | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/emacs/notmuch.el b/emacs/notmuch.el

[PATCH 3/8] emacs: Move search-target logic to `notmuch-search-show-result'

This is a simpler place to do this, since we can avoid any point motion and hence any save-excursions in `notmuch-search-process-filter', which in turn lets us put all of the search-target logic outside of any save-excursions. `notmuch-search-process-filter' could use some reindentation after this

[PATCH 2/8] emacs: Separate search line parsing and display

Previously, much of the display of search lines was done in the same function that parsed the CLI's output. Now the parsing function only parses, and notmuch-search-show-result fully inserts the search result in the search buffer. --- emacs/notmuch.el | 33 + 1 f

[PATCH 1/8] emacs: Clean up notmuch-search-show-result

This simplifies the code and makes it no longer cubic in the number of result fields. --- emacs/notmuch.el | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/emacs/notmuch.el b/emacs/notmuch.el index c6236db..be217a2 100644 --- a/emacs/notmuch.el +++ b/ema

[PATCH 0/8] JSON-based search-mode

This patch series replaces the text format parser used for search in Emacs with a parser for the JSON format. This should address the escaping and flexibility problems that have plagued the text format. Like the text format, it supports incremental output. Patches 1-4 simply clean up the Emacs se

Re: notmuch with the bbdb

On Tue, Jul 03 2012, Daniel Reusche wrote: > heyho. > in the documentation it said, bbdb would work really well with message > mode. my problem now is, that it is stated nowhere how to feed the > database of notmuch to the bbdb initially. > is there a way to export all the mail addresses in the

[PATCH 2/2] debian: document tag action invocation fix in changelog

--- debian/changelog |7 +++ 1 file changed, 7 insertions(+) diff --git a/debian/changelog b/debian/changelog index 0a57e7d..6fca693 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +notmuch (0.13.2-2) UNRELEASED; urgency=low + + [ Stefano Zacchiroli ] + * notmuch-m

[PATCH 1/2] notmuch-mutt: fix helper invocation for the tag action

As it was before, "-inbox" was interpreted as a getopt option, rather than as a tag manipulation request. Making the action unusable. Closes: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678012 --- contrib/notmuch-mutt/notmuch-mutt|2 +- contrib/notmuch-mutt/notmuch-mutt.rc |2 +-

notmuch-mutt: fix tag action invocation

Please find attached patches to fix a bug reported to the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678012 by Salvatore Bonaccorso (thanks!).

[PATCH 7/8] emacs: Implement an incremental JSON parser

This parser is designed to read streaming JSON whose structure is known to the caller. Like a typical JSON parsing interface, it provides a function to read a complete JSON value from the input. However, it extends this with an additional function that requires the next value in the input to be a

[PATCH 2/8] emacs: Separate search line parsing and display

Previously, much of the display of search lines was done in the same function that parsed the CLI's output. Now the parsing function only parses, and notmuch-search-show-result fully inserts the search result in the search buffer. --- emacs/notmuch.el | 33 + 1 f

[PATCH 1/8] emacs: Clean up notmuch-search-show-result

This simplifies the code and makes it no longer cubic in the number of result fields. --- emacs/notmuch.el | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/emacs/notmuch.el b/emacs/notmuch.el index c6236db..be217a2 100644 --- a/emacs/notmuch.el +++ b/ema

[PATCH 8/8] emacs: Switch from text to JSON format for search results

The JSON format eliminates the complex escaping issues that have plagued the text search format. This uses the incremental JSON parser so that, like the text parser, it can output search results incrementally. This slows down the parser by about ~4X, but puts us in a good position to optimize eit

[PATCH 6/8] test: New test for incremental search output parsing

This advises the search process filter to make it process one character at a time in order to test the pessimal case for incremental search output parsing. The text parser fails this test because it gets tricked into thinking a parenthetical remark in a subject is the tag list. --- test/emacs

[PATCH 5/8] emacs: Pass plist to `notmuch-search-show-result'

Rather than passing lots of arguments and then further passing those to `notmuch-search-insert-field', pass a plist containing all of the search result information. This plist is compatible JSON format search results. --- emacs/notmuch.el | 65 +++

[PATCH 4/8] emacs: Helper for reporting search parsing errors

This removes the last bit of direct output from the parsing function. With the parser now responsible solely for parsing, we can swap it out for another parser. --- emacs/notmuch.el | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/emacs/notmuch.el b/emacs/notmuch.el

[PATCH 3/8] emacs: Move search-target logic to `notmuch-search-show-result'

This is a simpler place to do this, since we can avoid any point motion and hence any save-excursions in `notmuch-search-process-filter', which in turn lets us put all of the search-target logic outside of any save-excursions. `notmuch-search-process-filter' could use some reindentation after this

[PATCH 0/8] JSON-based search-mode

This patch series replaces the text format parser used for search in Emacs with a parser for the JSON format. This should address the escaping and flexibility problems that have plagued the text format. Like the text format, it supports incremental output. Patches 1-4 simply clean up the Emacs se

[PATCH 2/2] debian: document tag action invocation fix in changelog

--- debian/changelog |7 +++ 1 file changed, 7 insertions(+) diff --git a/debian/changelog b/debian/changelog index 0a57e7d..6fca693 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +notmuch (0.13.2-2) UNRELEASED; urgency=low + + [ Stefano Zacchiroli ] + * notmuch-m

[PATCH 1/2] notmuch-mutt: fix helper invocation for the tag action

As it was before, "-inbox" was interpreted as a getopt option, rather than as a tag manipulation request. Making the action unusable. Closes: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678012 --- contrib/notmuch-mutt/notmuch-mutt|2 +- contrib/notmuch-mutt/notmuch-mutt.rc |2 +-

notmuch-mutt: fix tag action invocation

Please find attached patches to fix a bug reported to the Debian BTS http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678012 by Salvatore Bonaccorso (thanks!). ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmu

notmuch with the bbdb

heyho. in the documentation it said, bbdb would work really well with message mode. my problem now is, that it is stated nowhere how to feed the database of notmuch to the bbdb initially. is there a way to export all the mail addresses in the maildirs to plaintext files? bbdb-snarf gives a pret

[PATCH] Add missing "tags" field to search schema

This field is output by search, but it didn't make it into the documentation. --- devel/schemata |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/devel/schemata b/devel/schemata index 8fcab8e..06320f4 100644 --- a/devel/schemata +++ b/devel/schemata @@ -128,7 +128,8 @@ thre

Re: [RFC PATCH 00/14] modular mail stores based on URIs

On Sun, Jul 01 2012, Ethan wrote: >> I wonder if the following would be practical: use // as the field >> separator: >> >> e.g. mbox://filename//start_of_message+length >> >> I think 2 consecutive slashes // is about the only thing we can assume >> is not in the path or filename. Since it is not i

[RFC PATCH 00/14] modular mail stores based on URIs

k is referring. jamie. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120703/315ada97/attachment.pgp>