[PATCH 2/2] [python] fix unsafe utf-8 decodings

From: pazz This prevents unsafe calls to decode for return value None in get_authors/get_subject --- bindings/python/notmuch/tag.py|4 +++- bindings/python/notmuch/thread.py | 10 -- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/bindings/python/notmuch/tag.py

configure indentation width instead? (was: Re: [PATCH 2/2] Emacs: Add variable to toggle thread indentation to notmuch-show)

On Tue, 19 Jul 2011, Gregor Zattler wrote: > Hi Felix, notmuch develpers, > > Felix introduces a boolean configuration variable in order to > disable/enable indentation. Wouldn't it be more helpful and > powerful to customise the indentation width with "0" meaning no > indentation, "1" being the

queries switching from MH-E to notmuch

I'm considering switch emacs mailers, from MH-E to notmuch, as I would like to find an emacs mailer with decent IMAP support. Compared to gnus, notmuch seems much quicker, and I like the sound of tags + fast searching. Can anyone help with the following points: 1. Deleting emails I've seen the

[PATCH 2/2] [python] fix unsafe utf-8 decodings

From: pazz This prevents unsafe calls to decode for return value None in get_authors/get_subject --- bindings/python/notmuch/tag.py|4 +++- bindings/python/notmuch/thread.py | 10 -- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/bindings/python/notmuch/tag.py

Re: configure indentation width instead? (was: Re: [PATCH 2/2] Emacs: Add variable to toggle thread indentation to notmuch-show)

On Tue, 19 Jul 2011, Gregor Zattler wrote: > Hi Felix, notmuch develpers, > > Felix introduces a boolean configuration variable in order to > disable/enable indentation. Wouldn't it be more helpful and > powerful to customise the indentation width with "0" meaning no > indentation, "1" being the

Memory management issue in notmuch-haskell bindings

It seems that the notmuch-haskell bindings (version 0.2.2 built against notmuch from git master; passes notmuch-test) aren't dealing with memory management properly. In particular, the attached test code[1] causes talloc to abort. Unfortunately, while the issue is consistently reproducible, it onl

PATCH: (more) compability with emacs 22

Hi Currently, notmuch-lib.el does not have enough emacs < 23 compability functions. This patch makes notmuch better compatible with emacs 22: --8<8<8<8<8<8<8<8<8<8<-- diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el index f93c957..d6b4108 100644 --- a

Memory management issue in notmuch-haskell bindings

It seems that the notmuch-haskell bindings (version 0.2.2 built against notmuch from git master; passes notmuch-test) aren't dealing with memory management properly. In particular, the attached test code[1] causes talloc to abort. Unfortunately, while the issue is consistently reproducible, it onl

PATCH: (more) compability with emacs 22

Hi Currently, notmuch-lib.el does not have enough emacs < 23 compability functions. This patch makes notmuch better compatible with emacs 22: --8<8<8<8<8<8<8<8<8<8<-- diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el index f93c957..d6b4108 100644 --- a