[RFC][alot] design decisions

Hi all, with alot 0.3 released, I started thinking seriously about proper™ MIME-display and gnupg integration for alot. I have to make a few design decisions here and could really use some informed opinions from more experienced UI developers. My question in particular is: How do I best

Re: [PATCH 1/2] config: Add 'config list' command

On Wed, 21 Mar 2012 09:31:37 +1100, Peter Wang noval...@gmail.com wrote: Add a command to list all keys in a given configuration section. One use is as follows: a MUA may prefer to store data in a central notmuch configuration file so that the data is accessible across different machines,

[PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions

In case required gmime (2.4 or 2.6) version if not found print information about both alternatives (and currently minimal 2.6 version that is needed). --- This replaces id:1332281811-24710-2-git-send-email-tomi.oll...@iki.fi (having itself

[PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions

In case required gmime (2.4 or 2.6) version if not found print information about both alternatives (and currently minimal 2.6 version that is needed). --- This replaces id:1332281811-24710-2-git-send-email-tomi.oll...@iki.fi (having itself

[PATCH] NEWS: consistent 2-space indentation in new content

Some 0.12 NEWS items descriptions were indented with 3 spaces whereas all other lines are indented with 2 spaces. Brought those escaped lines back in line with others. --- NEWS | 16 1 files changed, 8 insertions(+), 8 deletions(-) diff --git a/NEWS b/NEWS index

Re: [PATCH 1/2] config: Add 'config list' command

On Wed, 21 Mar 2012 20:30:43 +0200, Tomi Ollila tomi.oll...@iki.fi wrote: On Wed, 21 Mar 2012 09:31:37 +1100, Peter Wang noval...@gmail.com wrote: Add a command to list all keys in a given configuration section. One use is as follows: a MUA may prefer to store data in a central notmuch

Questions from a user new to notmuch

I've been playing with notmuch for a couple days and am impressed so far. The virtual folder concept is taking some getting accustomed to but I see the inherent flexibility. Now, some new user questions. :) 1. Using offlineimap to store mail into a Maildir, is it safe to move an already

[PATCH] vim: fix regex after notmuch show output change

The new field excluded was added to the output and made this regex fail. --- vim/plugin/notmuch.vim |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim index 21985c7..92e1b50 100644 --- a/vim/plugin/notmuch.vim +++

[PATCH 2/2] configure: print info about required gmime 2.4 or 2.6 versions

In case required gmime (2.4 or 2.6) version if not found print information about both alternatives (and currently minimal 2.6 version that is needed). --- I'm not entirely happy about the implementation but I would be less happy to write static message that has the same spesific version

[PATCH 1/2] configure: add empty line after each missing component message

Currently whenever message about missing GMime, Glib or talloc is printed the message is 2 lines, component info and its http location in next line. In the future the amount of lines will vary. To ease reading in these cases newline is added after each message. --- configure |4 +++- 1 files

[PATCH 1/2] config: Add 'config list' command

Add a command to list all keys in a given configuration section. One use is as follows: a MUA may prefer to store data in a central notmuch configuration file so that the data is accessible across different machines, e.g. an addressbook. The list command helps to implement features such as tab

[PATCH 2/2] man: Document 'config list' command

Document the 'config list' command and its output. --- man/man1/notmuch-config.1 | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/man/man1/notmuch-config.1 b/man/man1/notmuch-config.1 index 395cb9c..b9f81a5 100644 --- a/man/man1/notmuch-config.1 +++

[RFC] Split notmuch_database_close into two functions

I propose to split the function notmuch_database_close into notmuch_database_close and notmuch_database_destroy so that long running processes like alot can close the database while still using data obtained from queries to that database. I've updated the tools, the go, ruby and python bindings

[PATCH 2/7] NEWS: Document the notmuch_database_close split

Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- NEWS | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/NEWS b/NEWS index ed5e3c5..26fce67 100644 --- a/NEWS +++ b/NEWS @@ -52,6 +52,18 @@ Reply improvement using the JSON format reply

[PATCH 3/7] Use notmuch_database_destroy instead of notmuch_database_close

Adapt the notmuch binaries source to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- notmuch-count.c |2 +- notmuch-dump.c|2 +- notmuch-new.c |2 +- notmuch-reply.c |2 +- notmuch-restore.c |2 +-

[PATCH 1/7] Split notmuch_database_close into two functions

Formerly notmuch_database_close closed the xapian database and destroyed the talloc structure associated with the notmuch database object. Split notmuch_database_close into notmuch_database_close and notmuch_database_destroy. This makes it possible for long running programs to close the xapian

[PATCH 4/7] Use notmuch_database_destroy instead of notmuch_database_close

Adapt notmuch-deliver to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- contrib/notmuch-deliver/src/main.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/contrib/notmuch-deliver/src/main.c

[PATCH 5/7] go: Use notmuch_database_destroy instead of notmuch_database_close

Adapt the go bindings to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- bindings/go/pkg/notmuch.go |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bindings/go/pkg/notmuch.go b/bindings/go/pkg/notmuch.go index

[PATCH 6/7] ruby: Use notmuch_database_destroy instead of notmuch_database_close

Adapt the ruby bindings to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- bindings/ruby/database.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/bindings/ruby/database.c b/bindings/ruby/database.c index

[PATCH 7/7] python: wrap and use notmuch_database_destroy as destructor

Adapt the go bindings to the notmuch_database_close split. Signed-off-by: Justus Winter <4winter at informatik.uni-hamburg.de> --- bindings/python/notmuch/database.py | 17 +++-- 1 files changed, 15 insertions(+), 2 deletions(-) diff --git a/bindings/python/notmuch/database.py

[PATCH v2 1/6] test: emacs: new tests "notmuch-show: {add, remove} multiple tags {to, from} single message"

Hi > * test/emacs: > > - Rename subtests "{Add,Remove} tag from notmuch-show view" to > "notmuch-show: {add,remove} single tag {to,from} single message" > to be consistent with the following tests. > > - New subtest "notmuch-show: add multiple tags to single message": >

[PATCH v2 4/6] emacs: add optional predicate arg to `notmuch-show-mapc'

On Fri, 24 Feb 2012 23:30:38 +0100, Pieter Praet wrote: > * emacs/notmuch-show.el (notmuch-show-mapc): > > If provided with optional argument PREDICATE, only call > FUNCTION if calling PREDICATE returns non-nil. > > Also correct original docstring: 's/thread/buffer/'. > --- >

[PATCH v2 5/6] emacs: simplify `notmuch-show-get-messages-ids{, -search}'

On Fri, 24 Feb 2012 23:30:39 +0100, Pieter Praet wrote: > * emacs/notmuch-show.el > > (notmuch-show-get-messages-ids): > If provided with optional arg SEPARATOR, return a string consisting > of all Message-Id's, separated by SEPARATOR. Also improve original > docstring wrt default

[PATCH v2 5/6] emacs: simplify `notmuch-show-get-messages-ids{, -search}'

On Fri, 24 Feb 2012 23:30:39 +0100, Pieter Praet wrote: > * emacs/notmuch-show.el > > (notmuch-show-get-messages-ids): > If provided with optional arg SEPARATOR, return a string consisting > of all Message-Id's, separated by SEPARATOR. Also improve original > docstring wrt default

[RFC] Split notmuch_database_close into two functions

Hi all, I can confirm that this fixes a rather nasty core dump in a branch of alot that closes and re-opens the database more frequently. /p

[RFC][alot] design decisions

Hi all, with alot 0.3 released, I started thinking seriously about proper? MIME-display and gnupg integration for alot. I have to make a few design decisions here and could really use some informed opinions from more experienced UI developers. My question in particular is: How do I best

[PATCH 1/2] config: Add 'config list' command

On Wed, 21 Mar 2012 09:31:37 +1100, Peter Wang wrote: > Add a command to list all keys in a given configuration section. > > One use is as follows: a MUA may prefer to store data in a central > notmuch configuration file so that the data is accessible across > different machines, e.g. an

[PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions

In case required gmime (2.4 or 2.6) version if not found print information about both alternatives (and currently minimal 2.6 version that is needed). --- This replaces id:"1332281811-24710-2-git-send-email-tomi.ollila at iki.fi" (having itself id:"1332281811-24710-2b-git-send-email-tomi.ollila

[PATCH 2b/2] configure: print info about required gmime 2.4 or 2.6 versions

In case required gmime (2.4 or 2.6) version if not found print information about both alternatives (and currently minimal 2.6 version that is needed). --- This replaces id:"1332281811-24710-2-git-send-email-tomi.ollila at iki.fi" (having itself id:"1332281811-24710-2b-git-send-email-tomi.ollila

[PATCH] NEWS: consistent 2-space indentation in new content

Some 0.12 NEWS items descriptions were indented with 3 spaces whereas all other lines are indented with 2 spaces. Brought those escaped lines back in line with others. --- NEWS | 16 1 files changed, 8 insertions(+), 8 deletions(-) diff --git a/NEWS b/NEWS index

Questions from a user new to notmuch

I've been playing with notmuch for a couple days and am impressed so far. The virtual folder concept is taking some getting accustomed to but I see the inherent flexibility. Now, some new user questions. :) 1. Using offlineimap to store mail into a Maildir, is it safe to move an already

[PATCH] vim: fix regex after "notmuch show" output change

The new field "excluded" was added to the output and made this regex fail. --- vim/plugin/notmuch.vim |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim index 21985c7..92e1b50 100644 --- a/vim/plugin/notmuch.vim +++