Re: [notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
* Sebastian Spaeth sebast...@sspaeth.de [Do Mär 04 14:57:27 +0100 2010] On 2010-03-04, Sebastian Spaeth wrote: The current code in json_quote_str() only accepts strict printable ASCII code points (i.e. 32-127), all other code points are dropped from the JSON output. That would explain

Re: [notmuch] [PATCH] notmuch-reply: Use a shorter 'On, X Y wrote:' line

2010-03-04 Thread Michal Sojka
Hi again, On Tue, 02 Mar 2010, Sebastian Spaeth wrote: Previously, we would output: 'On Thu, 25 Feb 2010 14:32:54 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote:' now it is: 'On 2010-02-25, Sebastian Spaeth wrote:' In case we don't find a '' (as indicator for 'Realname email'), we

[notmuch] Debian package

2010-03-04 Thread Xavier Maillard
Hi, I am using Debian GNU/linux SID and notmuch and I'd like to be bleading edge with notmuch. So I am trying to figure out whether someone is maintaining a Debian package against notmuch git repository or not. If the former, that's nice. Xavier ___

Re: [notmuch] Debian package

2010-03-04 Thread martin f krafft
also sprach Xavier Maillard x...@gnu.org [2010.03.05.0611 +0100]: I am using Debian GNU/linux SID and notmuch and I'd like to be bleading edge with notmuch. So I am trying to figure out whether someone is maintaining a Debian package against notmuch git repository or not. If the former, that's

[notmuch] [PATCH 2/2] Build and link against notmuch shared library

2010-03-04 Thread Sebastian Spaeth
> notmuch_client_modules = $(notmuch_client_srcs:.c=.o) > -notmuch: $(notmuch_client_modules) lib/notmuch.a > - $(call quiet,CXX,$(LDFLAGS)) $^ $(FINAL_LDFLAGS) -o $@ > +notmuch: $(notmuch_client_modules) lib/libnotmuch.so > + $(call quiet,CC,$(LDFLAGS)) -lnotmuch $(filter-out >

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
The current code in json_quote_str() only accepts strict printable ASCII code points (i.e. 32-127), all other code points are dropped from the JSON output. This patch accepts code points 32-255. json_quote_str() should handle non-ASCII characters. --- json.c |4 ++-- 1 files changed, 2

[notmuch] [PATCH] format_part_json: part_content->data is not null terminated

2010-03-04 Thread Gregor Hoffleit
In format_part_json, part_content->data is not a null terminated string. Instead, we have to use part_content->len. --- notmuch-show.c |7 ++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/notmuch-show.c b/notmuch-show.c index 1a1d601..4b755e9 100644 --- a/notmuch-show.c

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Sebastian Spaeth
On 2010-03-04, Sebastian Spaeth wrote: > The current code in json_quote_str() only accepts strict printable ASCII > code points (i.e. 32-127), all other code points are dropped from the > JSON output. That would explain why my web interface does not display any umlaut symbols. Nice finding,

[notmuch] [PATCH] json_quote_str should handle non-ASCII characters

2010-03-04 Thread Gregor Hoffleit
* Sebastian Spaeth [Do M?r 04 14:57:27 +0100 2010] > On 2010-03-04, Sebastian Spaeth wrote: > > The current code in json_quote_str() only accepts strict printable ASCII > > code points (i.e. 32-127), all other code points are dropped from the > > JSON output. > > That would explain why my web

[notmuch] [PATCH] notmuch-reply: Use a shorter 'On, X Y wrote:' line

2010-03-04 Thread Michal Sojka
Hi again, On Tue, 02 Mar 2010, Sebastian Spaeth wrote: > Previously, we would output: > 'On Thu, 25 Feb 2010 14:32:54 +0100, Sebastian Spaeth SSpaeth.de> wrote:' now it is: > 'On 2010-02-25, Sebastian Spaeth wrote:' > > In case we don't find a '<' (as indicator for 'Realname '), we still > use