[PATCH 2/2] test/test-lib.sh: launch smtp-dummy with --background and finally kill(1) it.

Take the new --background option of smtp-dummy to use so that it is known there is smtpd listener ready when it is needed. As the smtp-dummy instance is no longer child process of the script sending SIGKILL to it is the only way to make sure the instance exits when required. --- Resent after

[PATCH 1/2] test/smtp-dummy: add --background option for going background after listen(2)

To avoid the possibility that smtp-dummy doesn't have chance to bind its listening socket until something tries to send message to it this option makes caller wait until socket is already listening for connections. In case this --background option is used, the pid of running smtp-dummy is printed

Re: [alot] announcing v0.2 aka. robot santa

Thx Adrian Jamie! It would be great to get it into Debian, yes. I will have a look at Debian packaging if we don't find a more capable volunteer in the next few weeks. Thanks for your initial work on this. While we're at it: I heard that there are some build scripts for Arch and Gentoo

[PATCH] notmuch: unref charset_filter to fix one memory leak

In my use case g_object_unref(charset_filter) reduces memory consumption over 90% when 'notmuch show --format=text *' is executed (~11000 messages, RES ~330M - ~25M). --- notmuch-show.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/notmuch-show.c b/notmuch-show.c

Re: [alot] announcing v0.2 aka. robot santa

On Tue, 13 Dec 2011 10:38:46 +, Patrick Totzke patricktot...@googlemail.com wrote: I have seen this before yes. It seems to be a problem with the python distribution on debian. Apparently, you have two different versions of the argparse module installed: As of 2.7, argparse is part of

[PATCH 1/5] Fix comments about what is stored in the database

Commit 567bcbc2 introduced two new values for each message (content of the From and Subject headers), but the comments about the database schema had not been updated accordingly. --- lib/database.cc |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/lib/database.cc

[PATCH 0/5] Store message modification times in the DB

Hello world, This is a patch series I've been working on for some time in order to be able to sync my tags on several computers. I'm posting it now, but please consider it as a RFC rather than something that is ready to be pushed. The basic idea is to the last time each message was modified,

[PATCH 2/5] lib: Add a MTIME value to every mail document

This is a time_t value, similar to the message date (TIMESTAMP). It is first set when the message is added to the database, and is then updated every time a tag is added or removed. It can thus be used for doing incremental dumps of the database or for synchronizing it between several computers.

[PATCH 3/5] lib: Make MTIME values searchable

Tag modification times are now searchable as ranges (just like regular message dates) with the mtime: prefix. --- lib/database-private.h |1 + lib/database.cc|3 +++ notmuch.1 | 14 -- notmuch.c | 13 ++--- 4 files changed, 26

[PATCH 4/5] show: include mtime in JSON output

This could be used by a UI implementation somehow. --- notmuch-show.c |7 --- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/notmuch-show.c b/notmuch-show.c index 873a7c4..7279601 100644 --- a/notmuch-show.c +++ b/notmuch-show.c @@ -202,17 +202,18 @@ format_message_json

[PATCH 5/5] python: add get_mtime() to the Message class

--- bindings/python/notmuch/message.py | 20 1 files changed, 20 insertions(+), 0 deletions(-) diff --git a/bindings/python/notmuch/message.py b/bindings/python/notmuch/message.py index ce8e718..56f56c2 100644 --- a/bindings/python/notmuch/message.py +++

[PATCH v3 0/4] Several minor Emacs enhancements

Hi David et al., Here is a rebased version of this patch series, with more descriptive commit messages. Please tell me if there are still ways to enhance them. English is not my native language and it's sometimes hard to figure out what's relevant and how to word it :) Best regards, Thomas

[PATCH v3 1/4] emacs: Let the user choose where to compose new mails

Reusing the current window to compose a new mail may be troublesome for the user. This patch introduces a new customizable variable, notmuch-mua-compose-in, which lets the user choose where to create the mail buffer: in the current window (current and default behaviour), in a new window, or in a

[PATCH v3 3/4] emacs: rename notmuch-decimal-separator to notmuch-thousands-separator

In 123,456.78, . is the decimal separator, but , is the thousands separator. This commit also mentions the space being used as thousands separator in several European countries. --- emacs/notmuch-hello.el |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 2/4] emacs: Add a face for crypto parts headers

Commit cb841878 introduced new parts handlers for crypto parts, but also hardcoded values for their headers face. This replaces these hardcoded values with a customizable face. --- emacs/notmuch-crypto.el |5 + emacs/notmuch-show.el |4 ++-- 2 files changed, 7 insertions(+), 2

Re: [PATCH v3 4/4] emacs: add notmuch-hello-hook

On Tue, 13 Dec 2011 18:32:12 +0100, Thomas Jost schno...@schnouki.net wrote: This hook is called every time the notmuch-hello buffer is updated. --- emacs/notmuch-hello.el |9 - 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/emacs/notmuch-hello.el

Re: [PATCH v3 0/4] Several minor Emacs enhancements

On Tue, 13 Dec 2011 18:32:08 +0100, Thomas Jost schno...@schnouki.net wrote: Here is a rebased version of this patch series, with more descriptive commit messages. Hi, Thomas. Thanks for resending these. To be clear, this is not really a patch series as the four patches are completely

[PATCH] notmuch: unref charset_filter (once more) to fix one memory leak

From: Tomi Ollila tomi.oll...@iki.fi In my test case added g_object_unref(charset_filter) reduces memory consumption over 90% when 'notmuch show --format=text *' is executed (~11000 messages, RES ~330M - ~25M). --- Thanks Dmitry. I did not realize unref unreferences, does not deallocate

[PATCH] test: optionally print subtest number

From: David Bremner brem...@debian.org The idea is that $test_count could be used in tests to label intermediate files. The output enabled by this patch (and --debug) helps figure out which OUTPUT.nn file belongs to which test in case several subtests write to OUTPUT.$test_count --- Is there

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner da...@tethera.net wrote: From: David Bremner brem...@debian.org The idea is that $test_count could be used in tests to label intermediate files. The output enabled by this patch (and --debug) helps figure out which OUTPUT.nn file belongs to

[Alpha PATCH 2/6] test: add test for hex_(encode|decode)

From: David Bremner brem...@debian.org The test binary hex-xcode can also be used to check for memory leaks. --- test/.gitignore |1 + test/Makefile.local |6 +++- test/basic |2 +- test/hex-escaping | 20 + test/hex-xcode.c| 76

[Alpha PATCH 4/6] test: add test for dump --format=notmuch

From: David Bremner brem...@debian.org The first test is really to test our assumptions about the corpus, namely that a certain set of message-id's is safe (i.e. doesn't change under hex-escaping). We then check dump output as best we can without functionality-to-come in notmuch-restore. ---

New Dump/Restore Format

Hi All; There are some style/doc issues remaining, but because bugs in dump and restore really suck, I thought I would ask for early feedback on functionality. I'm particularly interested in how the new dump format works for weird message-ids (spaces and so on). If you have public messages with

[Alpha PATCH 1/6] util/hex-escape.[ch]: encoding/decoding strings into restricted character set

From: David Bremner brem...@debian.org The character set is chosen to be suitable for pathnames, and the same as that used by contrib/nmbug --- util/Makefile.local |2 +- util/hex-escape.c | 150 +++ util/hex-escape.h | 15 + 3 files

[Alpha PATCH 6/6] test: second set of dump/restore --format=notmuch tests

From: David Bremner brem...@debian.org These one need the completed functionality in notmuch-restore. Fairly exotic tags are tested, but no weird message id's. --- test/dump-restore | 33 + 1 files changed, 33 insertions(+), 0 deletions(-) diff --git

[Alpha PATCH 3/6] notmuch-dump: add --format=(notmuch|sup)

From: David Bremner brem...@debian.org sup is the old format, and remains the default. Each line of the notmuch format is msg_id tag tag...tag where each space seperated token is 'hex-encoded' to remove troubling characters. In particular this format won't have the same problem with e.g. spaces

[Alpha PATCH 5/6] notmuch-restore: add --format=notmuch support

From: David Bremner brem...@debian.org This is format is whitespace separated tokens, encoded by util/hex-escape.c --- notmuch-restore.c | 83 1 files changed, 64 insertions(+), 19 deletions(-) diff --git a/notmuch-restore.c

Re: [PATCH] test: optionally print subtest number

On Wed, 14 Dec 2011 00:15:43 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner da...@tethera.net wrote: From: David Bremner brem...@debian.org The idea is that $test_count could be used in tests to label intermediate files. The

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 22:55:18 +0200, Tomi Ollila tomi.oll...@iki.fi wrote: On Wed, 14 Dec 2011 00:15:43 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner da...@tethera.net wrote: From: David Bremner brem...@debian.org The idea

Re: [PATCH] test: optionally print subtest number

On Wed, 14 Dec 2011 00:58:35 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: On Tue, 13 Dec 2011 22:55:18 +0200, Tomi Ollila tomi.oll...@iki.fi wrote: On Wed, 14 Dec 2011 00:15:43 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: Looks good to me. Except for tabs

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner da...@tethera.net wrote: The idea is that $test_count could be used in tests to label intermediate files. The output enabled by this patch (and --debug) helps figure out which OUTPUT.nn file belongs to which test in case several subtests write

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 14:22:21 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: I've only been vaguely following this test count stuff, but I'm not sure I understand what's the point of giving tests a number that is ultimately mutable. Why not just label things by the test name,

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 19:18:16 -0400, David Bremner da...@tethera.net wrote: On Tue, 13 Dec 2011 14:22:21 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: I've only been vaguely following this test count stuff, but I'm not sure I understand what's the point of giving tests a

Re: [PATCH] test: optionally print subtest number

On Wed, 14 Dec 2011 03:24:23 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: BTW I have some plans to introduce optional explicit test ids that can be used for inter-test dependencies. E.g.: test_begin_subtest test-id-1 A subtest ;; in another test requre that

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:35:53 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: On Wed, 14 Dec 2011 03:24:23 +0400, Dmitry Kurochkin dmitry.kuroch...@gmail.com wrote: BTW I have some plans to introduce optional explicit test ids that can be used for inter-test dependencies.

Re: [PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:25:14 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: On Tue, 13 Dec 2011 19:18:16 -0400, David Bremner da...@tethera.net wrote: We don't actually have test names, at least not ones directly suitable for file names. I guess we could encode them or

Re: [PATCH v6 1/2] emacs: User-defined sections in notmuch-hello

Hi Daniel. I have finished reviewing this patch at last. Sorry, it is a bit messy. Overall, I like the patch. It is a very nice improvement. I am sure I have missed some important points, but I guess this is the best I can do right now. Perhaps I will find more comments for the next version

[PATCH v2] emacs: support "notmuch new" as a notmuch-poll-script

Hi Jani. On Mon, 12 Dec 2011 21:57:28 +0200, Jani Nikula wrote: > Support nil value for notmuch-poll-script to run "notmuch new" instead of > an external script, and make this the new default. "notmuch new" is run > using the configured notmuch-command. > > This allows taking better advantage

[PATCH v3] emacs: support "notmuch new" as a notmuch-poll-script

On Mon, 12 Dec 2011 22:50:04 +0200, Jani Nikula wrote: > Support nil value for notmuch-poll-script to run "notmuch new" instead of > an external script, and make this the new default. "notmuch new" is run > using the configured notmuch-command. > > This allows taking better advantage of the

[PATCH v3] emacs: support "notmuch new" as a notmuch-poll-script

On Mon, 12 Dec 2011 16:24:51 -0500, Austin Clements wrote: > Quoth Jani Nikula on Dec 12 at 11:13 pm: > > On Tue, 13 Dec 2011 00:53:05 +0400, Dmitry Kurochkin > gmail.com> wrote: > > > On Mon, 12 Dec 2011 22:50:04 +0200, Jani Nikula > > > wrote: > > > > +If set to nil (the default), new mail

[PATCH 1/2] test/smtp-dummy: add --background option for going background after listen(2)

To avoid the possibility that smtp-dummy doesn't have chance to bind its listening socket until something tries to send message to it this option makes caller wait until socket is already listening for connections. In case this --background option is used, the pid of running smtp-dummy is printed

[PATCH 2/2] test/test-lib.sh: launch smtp-dummy with --background and finally kill(1) it.

Take the new --background option of smtp-dummy to use so that it is known there is smtpd listener ready when it is needed. As the smtp-dummy instance is no longer child process of the script sending SIGKILL to it is the only way to make sure the instance exits when required. --- test/test-lib.sh

[PATCH 2/2] test/test-lib.sh: launch smtp-dummy with --background and finally kill(1) it.

Take the new --background option of smtp-dummy to use so that it is known there is smtpd listener ready when it is needed. As the smtp-dummy instance is no longer child process of the script sending SIGKILL to it is the only way to make sure the instance exits when required. --- Resent after

[PATCH 1/2] test/smtp-dummy: add --background option for going background after listen(2)

To avoid the possibility that smtp-dummy doesn't have chance to bind its listening socket until something tries to send message to it this option makes caller wait until socket is already listening for connections. In case this --background option is used, the pid of running smtp-dummy is printed

[alot] announcing v0.2 aka. "robot santa"

Thx Adrian & Jamie! It would be great to get it into Debian, yes. I will have a look at Debian packaging if we don't find a more capable volunteer in the next few weeks. Thanks for your initial work on this. While we're at it: I heard that there are some build scripts for Arch and Gentoo

[PATCH] notmuch: unref charset_filter to fix one memory leak

In my use case g_object_unref(charset_filter) reduces memory consumption over 90% when 'notmuch show --format=text "*"' is executed (~11000 messages, RES ~330M -> ~25M). --- notmuch-show.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/notmuch-show.c b/notmuch-show.c

[PATCH] notmuch: unref charset_filter to fix one memory leak

On Tue, 13 Dec 2011 14:03:33 +0200, Tomi Ollila wrote: > In my use case g_object_unref(charset_filter) reduces memory > consumption over 90% when 'notmuch show --format=text "*"' is > executed (~11000 messages, RES ~330M -> ~25M). > --- > notmuch-show.c |4 +++- > 1 files changed, 3

[alot] announcing v0.2 aka. "robot santa"

ication/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20111213/7b26689e/attachment.pgp>

[PATCH v3 0/4] Several minor Emacs enhancements

Hi David et al., Here is a rebased version of this patch series, with more descriptive commit messages. Please tell me if there are still ways to enhance them. English is not my native language and it's sometimes hard to figure out what's relevant and how to word it :) Best regards, Thomas

[PATCH v3 1/4] emacs: Let the user choose where to compose new mails

Reusing the current window to compose a new mail may be troublesome for the user. This patch introduces a new customizable variable, notmuch-mua-compose-in, which lets the user choose where to create the mail buffer: in the current window (current and default behaviour), in a new window, or in a

[PATCH v3 3/4] emacs: rename notmuch-decimal-separator to notmuch-thousands-separator

In 123,456.78, "." is the decimal separator, but "," is the thousands separator. This commit also mentions the space being used as thousands separator in several European countries. --- emacs/notmuch-hello.el |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v3 2/4] emacs: Add a face for crypto parts headers

Commit cb841878 introduced new parts handlers for crypto parts, but also hardcoded values for their headers face. This replaces these hardcoded values with a customizable face. --- emacs/notmuch-crypto.el |5 + emacs/notmuch-show.el |4 ++-- 2 files changed, 7 insertions(+), 2

[PATCH v3 4/4] emacs: add notmuch-hello-hook

This hook is called every time the notmuch-hello buffer is updated. --- emacs/notmuch-hello.el |9 - 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el index 0fe9c1d..112b40b 100644 --- a/emacs/notmuch-hello.el +++

[PATCH v3 4/4] emacs: add notmuch-hello-hook

On Tue, 13 Dec 2011 18:32:12 +0100, Thomas Jost wrote: > This hook is called every time the notmuch-hello buffer is updated. > --- > emacs/notmuch-hello.el |9 - > 1 files changed, 8 insertions(+), 1 deletions(-) > > diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el >

[PATCH v3 0/4] Several minor Emacs enhancements

- 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/20111213/c995404c/attachment.pgp>

[PATCH] notmuch: unref charset_filter (once more) to fix one memory leak

From: Tomi Ollila In my test case added g_object_unref(charset_filter) reduces memory consumption over 90% when 'notmuch show --format=text "*"' is executed (~11000 messages, RES ~330M -> ~25M). --- Thanks Dmitry. I did not realize unref unreferences, does not deallocate

[PATCH] notmuch: unref charset_filter (once more) to fix one memory leak

On Tue, 13 Dec 2011 20:18:48 +0200, tomi.ollila at iki.fi wrote: > From: Tomi Ollila > > In my test case added g_object_unref(charset_filter) reduces memory > consumption over 90% when 'notmuch show --format=text "*"' is > executed (~11000 messages, RES ~330M -> ~25M). > --- > Thanks Dmitry. I

[PATCH] test: optionally print subtest number

From: David Bremner The idea is that $test_count could be used in tests to label intermediate files. The output enabled by this patch (and --debug) helps figure out which OUTPUT.nn file belongs to which test in case several subtests write to OUTPUT.$test_count --- Is there

[Alpha PATCH 2/6] test: add test for hex_(encode|decode)

From: David Bremner The test binary hex-xcode can also be used to check for memory leaks. --- test/.gitignore |1 + test/Makefile.local |6 +++- test/basic |2 +- test/hex-escaping | 20 + test/hex-xcode.c| 76

[Alpha PATCH 4/6] test: add test for dump --format=notmuch

From: David Bremner The first test is really to test our assumptions about the corpus, namely that a certain set of message-id's is safe (i.e. doesn't change under hex-escaping). We then check dump output as best we can without functionality-to-come in notmuch-restore. ---

New Dump/Restore Format

Hi All; There are some style/doc issues remaining, but because bugs in dump and restore really suck, I thought I would ask for early feedback on functionality. I'm particularly interested in how the new dump format works for weird message-ids (spaces and so on). If you have public messages with

[Alpha PATCH 1/6] util/hex-escape.[ch]: encoding/decoding strings into restricted character set

From: David Bremner The character set is chosen to be suitable for pathnames, and the same as that used by contrib/nmbug --- util/Makefile.local |2 +- util/hex-escape.c | 150 +++ util/hex-escape.h | 15 + 3

[Alpha PATCH 6/6] test: second set of dump/restore --format=notmuch tests

From: David Bremner These one need the completed functionality in notmuch-restore. Fairly exotic tags are tested, but no weird message id's. --- test/dump-restore | 33 + 1 files changed, 33 insertions(+), 0 deletions(-) diff --git

[Alpha PATCH 3/6] notmuch-dump: add --format=(notmuch|sup)

From: David Bremner sup is the old format, and remains the default. Each line of the notmuch format is "msg_id tag tag...tag" where each space seperated token is 'hex-encoded' to remove troubling characters. In particular this format won't have the same problem with e.g.

[Alpha PATCH 5/6] notmuch-restore: add --format=notmuch support

From: David Bremner This is format is whitespace separated tokens, encoded by util/hex-escape.c --- notmuch-restore.c | 83 1 files changed, 64 insertions(+), 19 deletions(-) diff --git a/notmuch-restore.c

[PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner wrote: > From: David Bremner > > The idea is that $test_count could be used in tests to label > intermediate files. The output enabled by this patch (and --debug) > helps figure out which OUTPUT.nn file belongs to which test in case > several

[PATCH] test: optionally print subtest number

On Wed, 14 Dec 2011 00:15:43 +0400, Dmitry Kurochkin wrote: > On Tue, 13 Dec 2011 15:56:47 -0400, David Bremner > wrote: > > From: David Bremner > > > > The idea is that $test_count could be used in tests to label > > intermediate files. The output enabled by this patch (and --debug) > >

[PATCH] test: optionally print subtest number

On Wed, 14 Dec 2011 00:58:35 +0400, Dmitry Kurochkin wrote: > On Tue, 13 Dec 2011 22:55:18 +0200, Tomi Ollila wrote: > > On Wed, 14 Dec 2011 00:15:43 +0400, Dmitry Kurochkin > gmail.com> wrote: > > > > > > Looks good to me. Except for tabs taking too much space. Perhaps the > > > following

[PATCH] test: optionally print subtest number

of number/name mapping, which will change over time. 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/20111213/b1964bd7/attachment.pgp>

[PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 14:22:21 -0800, Jameson Graef Rollins wrote: > I've only been vaguely following this "test count" stuff, but I'm not > sure I understand what's the point of giving tests a number that is > ultimately mutable. Why not just label things by the test name, instead > of the

[PATCH] test: optionally print subtest number

crypto symbol-hiding search-folder-coherence atomicity python hooks argument-parsing " -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.

[PATCH] test: optionally print subtest number

Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20111213/f59534cd/attachment.pgp>

[PATCH] test: optionally print subtest number

On Tue, 13 Dec 2011 15:25:14 -0800, Jameson Graef Rollins wrote: > On Tue, 13 Dec 2011 19:18:16 -0400, David Bremner > wrote: > > We don't actually have test names, at least not ones directly suitable > > for file names. I guess we could encode them or something, is that what > > you mean? >