On Wed, May 23 2012, Tellman wrote:
> Thanks for the quick response.
>
> I have gmime 2.4 installed.
Gmime 2.4.x -- what is the value if 'x' :D ?
> I tried the search and show commands and the responses all looked OK to
> me, although I wasn't quite sure what to look for. I didn't see any
> er
Jani Nikula writes:
> Add a multi-purpose address_match() function for matching strings
> against user's configured primary and other email addresses. Add thin
> wrappers user_address_in_string() and string_in_user_address() for
> ease of use, and also convert existing address_is_users() to wrapp
Austin Clements writes:
> Previously this function would create directory documents if they
> didn't exist. As a result, it could only be used on writable
> databases. This adds an argument to make creation optional and to
> make this function work on read-only databases. We use a flag
> argum
Tomi Ollila writes:
>
> File .../emacs-23.3/lisp/gnus/mm-uu.el mentions:
> "`gnus-decoded' is a fake charset, which means no further decoding."
> ---
>
pushed.
d
Felipe Contreras writes:
> I don't see how this patch could be fixed properly easily, and it was
> labeled as a hack, and I didn't like it in the first place anyway, so
> I'm going to revert it by tomorrow if I don't hear any good reason not
> to.
I think this highlights the need for at least a
Add tests for picking up user's From address from fallback headers
Envelope-To, X-Original-To, and Delivered-To.
Signed-off-by: Jani Nikula
---
test/reply | 55 +++
1 file changed, 55 insertions(+)
diff --git a/test/reply b/test/reply
index
Add another fallback header Delivered-To for guessing the user's from
address for notmuch reply before using the Received
headers. Apparently some MTAs use Delivered-To instead of
X-Original-To (which already exists as a fallback).
Reported-by: Michael Hudson-Doyle
Signed-off-by: Jani Nikula
---
id:"21a946917c5c8dd63295b7c87b7c2d1ebcb6e71e.1336746160.git.j...@nikula.org"
rebased against current master. No changes since v1.
BR,
Jani.
Jani Nikula (2):
cli: also use Delivered-To header to figure out the reply from
address
test: add tests for notmuch reply From guessing
notmuch-rep
Jani Nikula writes:
> Add a multi-purpose address_match() function for matching strings
> against user's configured primary and other email addresses. Add thin
> wrappers user_address_in_string() and string_in_user_address() for
> ease of use, and also convert existing address_is_users() to wrapp
Austin Clements writes:
> Previously this function would create directory documents if they
> didn't exist. As a result, it could only be used on writable
> databases. This adds an argument to make creation optional and to
> make this function work on read-only databases. We use a flag
> argum
Tomi Ollila writes:
>
> File .../emacs-23.3/lisp/gnus/mm-uu.el mentions:
> "`gnus-decoded' is a fake charset, which means no further decoding."
> ---
>
pushed.
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/
On Wed, May 23 2012, Tellman wrote:
> I recently installed notmuch on my OS X laptop. Searching works fine--it
> seems to find all my mail and displays the subject lines, dates, etc.,
> correctly.
> However, the emacs mode is unable to display the contents of any of the
> messages. I see the s
Felipe Contreras writes:
> I don't see how this patch could be fixed properly easily, and it was
> labeled as a hack, and I didn't like it in the first place anyway, so
> I'm going to revert it by tomorrow if I don't hear any good reason not
> to.
I think this highlights the need for at least a
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
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
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
This simplifies some more interfaces and gets rid of another #ifdef.
---
mime-node.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/mime-node.c b/mime-node.c
index ba3a01b..a838224 100644
--- a/mime-node.c
+++ b/mime-node.c
@@ -33,8 +33,7 @@ typedef struc
gmime 2.4 defines GMimeCipherContext, while 2.6 defines
GMimeCryptoContext. We can use a typedef to cover this discrepancy
and remove a bunch of #ifdefs.
---
mime-node.c |8
notmuch-client.h | 10 ++
2 files changed, 2 insertions(+), 16 deletions(-)
diff --git a/mime-
Ok, hopefully last version. This addresses Jani's latest comments.
The first patch uses a typedef to handle the incompatibility between
the crypto context between GMIME 2.4 and 2.6. We probably should have
done this originally, as it gets rid of a bunch of #ifdefs, and should
help reduce confusi
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 |3 +--
notmuch-reply.c | 29 -
notmuch-show.c | 30 +-
3 files changed, 34 insert
This simplifies the interface considerably, getting rid of #ifdefs
along the way.
---
mime-node.c |7 +++
notmuch-client.h | 10 +-
notmuch-reply.c |6 ++
notmuch-show.c |3 +--
4 files changed, 11 insertions(+), 15 deletions(-)
diff --git a/mime-node.c b/mim
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
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
This simplifies some more interfaces and gets rid of another #ifdef.
---
mime-node.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/mime-node.c b/mime-node.c
index ba3a01b..a838224 100644
--- a/mime-node.c
+++ b/mime-node.c
@@ -33,8 +33,7 @@ typedef struc
This simplifies the interface considerably, getting rid of #ifdefs
along the way.
---
mime-node.c |7 +++
notmuch-client.h | 10 +-
notmuch-reply.c |6 ++
notmuch-show.c |3 +--
4 files changed, 11 insertions(+), 15 deletions(-)
diff --git a/mime-node.c b/mim
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 |3 +--
notmuch-reply.c | 29 -
notmuch-show.c | 30 +-
3 files changed, 34 insert
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
gmime 2.4 defines GMimeCipherContext, while 2.6 defines
GMimeCryptoContext. We can use a typedef to cover this discrepancy
and remove a bunch of #ifdefs.
---
mime-node.c |8
notmuch-client.h | 10 ++
2 files changed, 2 insertions(+), 16 deletions(-)
diff --git a/mime-
Ok, hopefully last version. This addresses Jani's latest comments.
The first patch uses a typedef to handle the incompatibility between
the crypto context between GMIME 2.4 and 2.6. We probably should have
done this originally, as it gets rid of a bunch of #ifdefs, and should
help reduce confusi
On Tue, May 15, 2012 at 5:15 AM, Karl Harris wrote:
> I am trying the notmuch-vim-ruby plugin for the first time. Previously, I
> had been using the vim plugin that comes with notmuch.
>
> If I type :NotMuchR in vim, I get the following error messages:
> --
> Error detected while
On Mon, May 7, 2012 at 5:02 PM, Ali Polatel wrote:
> - Make mkmf use the notmuch.h under ../../lib
> - Use libnotmuch.a instead of linking to the installed libnotmuch.so
How has this ever worked?
libnotmuch.so links to many things, fortunately when linking Ruby's
notmuch.so binding to libnotmuch
Hi Doug,
Doug Penner writes:
> 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
Hi Austin :)
Quoting Austin Clements (2012-05-18 06:13:33)
> 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 c
Tomi Ollila writes:
> When mail message is read from emacs, the message structure
> obtained may contain parts which have content included
> (`text/plain` for example) and other parts where content is not
> included (`text/html` for example).
>
> In case content is included, the string is already
Tomi Ollila writes:
> 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 exc
Thanks for the quick response.
I have gmime 2.4 installed.
I tried the search and show commands and the responses all looked OK to me,
although I wasn't quite sure what to look for. I didn't see any error messages.
Here's a sample:
[[[{"id": "5qt490ipfnbu1z@78ca391a1b82.ant.amazon.com",
Forgot to mention that it implies --verify.
---
man/man1/notmuch-show.1 |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man1/notmuch-show.1 b/man/man1/notmuch-show.1
index a7f0792..03a99ea 100644
--- a/man/man1/notmuch-show.1
+++ b/man/man1/notmuch-show.1
@@ -130,7 +130,
Forgot to mention that it implies --verify.
---
man/man1/notmuch-show.1 |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man1/notmuch-show.1 b/man/man1/notmuch-show.1
index a7f0792..03a99ea 100644
--- a/man/man1/notmuch-show.1
+++ b/man/man1/notmuch-show.1
@@ -130,7 +130,
---
configure |4
1 file changed, 4 insertions(+)
diff --git a/configure b/configure
index 71981b7..5602be2 100755
--- a/configure
+++ b/configure
@@ -114,6 +114,10 @@ Fine tuning of some installation directories is available:
--bashcompletiondir=DIR Bash completions files
[SYSC
---
configure |4
1 file changed, 4 insertions(+)
diff --git a/configure b/configure
index 71981b7..5602be2 100755
--- a/configure
+++ b/configure
@@ -114,6 +114,10 @@ Fine tuning of some installation directories is available:
--bashcompletiondir=DIR Bash completions files
[SYSC
Thanks for the quick response.
I have gmime 2.4 installed.
I tried the search and show commands and the responses all looked OK to me,
although I wasn't quite sure what to look for. I didn't see any error messages.
Here's a sample:
[[[{"id": "5qt490ipfnbu1z.fsf at 78ca391a1b82.ant.amazon.com
egards,
> -Michal
> ___
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120523/a9b921d1/attachment.pgp>
On Tue, May 22 2012, Jani Nikula wrote:
>> +/* for the specified protocol return the context pointer (initializing
>> + * if needed) */
>> +GMimeCryptoContext *
>> +notmuch_crypto_get_context (notmuch_crypto_t *crypto, const char
> *protocol)
>> +{
>> +GMimeCryptoContext *cryptoctx = NULL;
>
>
ent was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120523/8d6791ec/attachment.pgp>
;
> }
>
> +GMimeCryptoContext *
> +notmuch_crypto_get_context (notmuch_crypto_t *crypto, const char
*protocol);
> +
> +int
> +notmuch_crypto_cleanup (notmuch_crypto_t *crypto);
> +
> int
> notmuch_count_command (void *ctx, int argc, char *argv[]);
>
> --
> 1.7.10
>
> ___
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
-- next part --
An HTML attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20120523/ceb6067b/attachment-0001.html>
On Wed, May 23 2012, Tellman wrote:
> I recently installed notmuch on my OS X laptop. Searching works fine--it
> seems to find all my mail and displays the subject lines, dates, etc.,
> correctly.
> However, the emacs mode is unable to display the contents of any of the
> messages. I see the s
I recently installed notmuch on my OS X laptop. Searching works fine--it seems
to find all my mail and displays the subject lines, dates, etc., correctly.
However, the emacs mode is unable to display the contents of any of the
messages. I see the subjects correctly, but when I try to view the
I recently installed notmuch on my OS X laptop. Searching works fine--it seems
to find all my mail and displays the subject lines, dates, etc., correctly.
However, the emacs mode is unable to display the contents of any of the
messages. I see the subjects correctly, but when I try to view the
try alot: multiple accounts [0] for free
/p
[0] http://alot.readthedocs.org/en/latest/configuration/index.html#accounts
Quoting Michal Sojka (2012-05-23 11:29:27)
> Hi Doug,
>
> Doug Penner writes:
> > I am in the process of trying to migrate from alpine (which handles
> > separate accounts *
Hi Austin :)
Quoting Austin Clements (2012-05-18 06:13:33)
> 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 c
Hi Doug,
Doug Penner writes:
> 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
Tomi Ollila writes:
> When mail message is read from emacs, the message structure
> obtained may contain parts which have content included
> (`text/plain` for example) and other parts where content is not
> included (`text/html` for example).
>
> In case content is included, the string is already
Tomi Ollila writes:
> 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 exc
53 matches
Mail list logo
