[PATCH 0/9] Fix directory lookup on read-only databases

Austin Clements writes: > This fixes notmuch_database_get_directory and > notmuch_database_find_message_by_filename so that they don't attempt > to create missing directory documents. This makes them work on > read-only databases (and prevents n_d_f_m_b_f from crashing > unceremoniously on read-

Re: [PATCH v3 1/6] cli: new crypto structure to store crypto contexts and parameters, and functions to support it

On May 23, 2012 4:44 AM, "Jameson Graef Rollins" wrote: > > This new structure, notmuch_crypto_t, keeps all relevant crypto > contexts and parameters together, and will make it easier to pass the > stuff around and clean it up. The name of the crypto context inside > this new struct will change,

[PATCH v3 1/6] cli: new crypto structure to store crypto contexts and parameters, and functions to support it

This new structure, notmuch_crypto_t, keeps all relevant crypto contexts and parameters together, and will make it easier to pass the stuff around and clean it up. The name of the crypto context inside this new struct will change, to reflect that it is actually a GPG context, which is a sub type o

[PATCH v3 3/6] cli: modify mime_node_open to take new crypto struct as argument

This simplifies the interface considerably, getting rid of #ifdefs along the way. --- mime-node.c | 11 +++ notmuch-client.h | 14 +- notmuch-reply.c |6 ++ notmuch-show.c |3 +-- 4 files changed, 11 insertions(+), 23 deletions(-) diff --git a/mime-node

[PATCH v3 5/6] cli: new crypto verify flag to handle verification

Use this flag rather than depend on the existence of an initialized gpgctx, to determine whether we should verify a multipart/signed. We will be moving to create the ctx lazily, so we don't want to depend on it being previously initialized if it's not needed. --- mime-node.c |5 ++--- no

[PATCH v3 2/6] cli: modify show and reply to use new crypto struct

notmuch_show_params_t is modified to use the new notmuch_crypto_t, and notmuch-show and notmuch-reply are modified accordingly. --- notmuch-client.h |7 +-- notmuch-reply.c | 29 - notmuch-show.c | 30 +- 3 files changed, 34 in

[PATCH v3 6/6] cli: use new notmuch_crypto_get_context in mime-node.c

This has the affect of lazily creating the crypto contexts only when needed. This removes code duplication from notmuch-show and notmuch-reply, and should speed up these functions considerably if the crypto flags are provided but the messages don't have any cryptographic parts. --- mime-node.c

[PATCH v3 0/6] cli: improved crypto internals

Third version of this series [0]. I've made some changes in this version: * added a new crypto.c that holds two functions: one to return a context for a specified crypto protocol (and initialize it if needed), and another to cleanup a crypto struct. This is introduced in the first patch, a

[PATCH v3 4/6] cli: modify mime_node_context to use the new crypto struct

This simplifies some more interfaces and gets rid of another #ifdef. --- mime-node.c | 22 -- 1 file changed, 8 insertions(+), 14 deletions(-) diff --git a/mime-node.c b/mime-node.c index 183ff5d..a838224 100644 --- a/mime-node.c +++ b/mime-node.c @@ -33,12 +33,7 @@ typedef

[PATCH v3 6/6] cli: use new notmuch_crypto_get_context in mime-node.c

This has the affect of lazily creating the crypto contexts only when needed. This removes code duplication from notmuch-show and notmuch-reply, and should speed up these functions considerably if the crypto flags are provided but the messages don't have any cryptographic parts. --- mime-node.c

[PATCH v3 5/6] cli: new crypto verify flag to handle verification

Use this flag rather than depend on the existence of an initialized gpgctx, to determine whether we should verify a multipart/signed. We will be moving to create the ctx lazily, so we don't want to depend on it being previously initialized if it's not needed. --- mime-node.c |5 ++--- no

[PATCH v3 4/6] cli: modify mime_node_context to use the new crypto struct

This simplifies some more interfaces and gets rid of another #ifdef. --- mime-node.c | 22 -- 1 file changed, 8 insertions(+), 14 deletions(-) diff --git a/mime-node.c b/mime-node.c index 183ff5d..a838224 100644 --- a/mime-node.c +++ b/mime-node.c @@ -33,12 +33,7 @@ typedef

[PATCH v3 3/6] cli: modify mime_node_open to take new crypto struct as argument

This simplifies the interface considerably, getting rid of #ifdefs along the way. --- mime-node.c | 11 +++ notmuch-client.h | 14 +- notmuch-reply.c |6 ++ notmuch-show.c |3 +-- 4 files changed, 11 insertions(+), 23 deletions(-) diff --git a/mime-node

[PATCH v3 2/6] cli: modify show and reply to use new crypto struct

notmuch_show_params_t is modified to use the new notmuch_crypto_t, and notmuch-show and notmuch-reply are modified accordingly. --- notmuch-client.h |7 +-- notmuch-reply.c | 29 - notmuch-show.c | 30 +- 3 files changed, 34 in

[PATCH v3 1/6] cli: new crypto structure to store crypto contexts and parameters, and functions to support it

This new structure, notmuch_crypto_t, keeps all relevant crypto contexts and parameters together, and will make it easier to pass the stuff around and clean it up. The name of the crypto context inside this new struct will change, to reflect that it is actually a GPG context, which is a sub type o

[PATCH v3 0/6] cli: improved crypto internals

Third version of this series [0]. I've made some changes in this version: * added a new crypto.c that holds two functions: one to return a context for a specified crypto protocol (and initialize it if needed), and another to cleanup a crypto struct. This is introduced in the first patch, a

Sending from multiple accounts

I am in the process of trying to migrate from alpine (which handles separate accounts *very* distinctly) to notmuch (which combines them). I have no problem with incoming e-mails being combined (actually looking forward to it) but am having a little trouble configuring outgoing e-mails to work

Sending from multiple accounts

I am in the process of trying to migrate from alpine (which handles separate accounts *very* distinctly) to notmuch (which combines them). I have no problem with incoming e-mails being combined (actually looking forward to it) but am having a little trouble configuring outgoing e-mails to work

emacs complains about encoding?

Michal Sojka writes: > Hello Adam, > > Adam Wolfe Gordon writes: >> It turns out it's actually not the emacs side, but an interaction >> between our JSON reply format and emacs. >> >> The JSON reply (and show) code includes part content for all text/* >> parts except text/html. Because all JSON

emacs complains about encoding?

Hello Adam, Adam Wolfe Gordon writes: > It turns out it's actually not the emacs side, but an interaction > between our JSON reply format and emacs. > > The JSON reply (and show) code includes part content for all text/* > parts except text/html. Because all JSON is required to be UTF-8, it > han

Re: [PATCH 0/9] Fix directory lookup on read-only databases

Austin Clements writes: > This fixes notmuch_database_get_directory and > notmuch_database_find_message_by_filename so that they don't attempt > to create missing directory documents. This makes them work on > read-only databases (and prevents n_d_f_m_b_f from crashing > unceremoniously on read-

Re: emacs complains about encoding?

Michal Sojka writes: > Hello Adam, > > Adam Wolfe Gordon writes: >> It turns out it's actually not the emacs side, but an interaction >> between our JSON reply format and emacs. >> >> The JSON reply (and show) code includes part content for all text/* >> parts except text/html. Because all JSON

Re: emacs complains about encoding?

Hello Adam, Adam Wolfe Gordon writes: > It turns out it's actually not the emacs side, but an interaction > between our JSON reply format and emacs. > > The JSON reply (and show) code includes part content for all text/* > parts except text/html. Because all JSON is required to be UTF-8, it > han