The previous json patches forgot to add the notmuch tags to the json output.
This is inconsistent to the text output so here they are. We just output a
'tags' field that sends notmuch tags as a json array.
Signed-off-by: Sebastian Spaeth sebast...@sspaeth.de
---
notmuch-show.c | 13
On Thu, 11 Mar 2010 13:11:43 +0100, Sebastian Spaeth sebast...@sspaeth.de
wrote:
The previous json patches forgot to add the notmuch tags to the json output.
This is inconsistent to the text output so here they are. We just output a
'tags' field that sends notmuch tags as a json array.
On Thu, 11 Mar 2010 17:22:41 +0100, Michal Sojka sojk...@fel.cvut.cz wrote:
thanks for clarification. It all sounds reasonable. The only problem I
can see now is that if I create a new account on my machine and run
emacs there, then the value of user-mail-address is login@hostname
which
Hey all,
Here's a rebased version of my shared library patch. It's pretty similar to the
last version and should build against a clean tree (I'd recommend git clean
-fxd).
Let me know if you have any build issues.
In the eyes of the powers that be, what is the long-term status of this patch?
On Thu, 11 Mar 2010, Ben Gamari wrote:
While the notmuch command-line interface is fantastic, there defintely are a few
gaps which hurt performance. Since I've been following, I've seen several
threads on how to handle message addition and initial tagging[1][2]. I recall
that some time ago Carl
On Thu, 11 Mar 2010 17:52:34 -0500 (EST), David A Benjamin david...@mit.edu
wrote:
To avoid breaking the current behavior, what if the set of tags applied to
new/moved/deleted(?) messages could be set on the command line or some
other library interface, while just perhaps defaulting to
The previous json patches forgot to add the notmuch tags to the json output.
This is inconsistent to the text output so here they are. We just output a
'tags' field that sends notmuch tags as a json array.
Signed-off-by: Sebastian Spaeth
---
notmuch-show.c | 13 -
1 files
I pushed this, (after wrapping the above commit message just a
bit).
-Carl
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachme
Hi,
On Wed, 10 Mar 2010, Aneesh Kumar K.V wrote:
> From: Aneesh Kumar K.V
>
> This patch add --recipient=all|sender option
>
> Signed-off-by: Aneesh Kumar K.V
> ---
> notmuch-client.h |2 +
> notmuch-reply.c | 55 -
> 2 files
Hi James,
On Tue, 09 Mar 2010, James Vasile wrote:
> When notmuch creates a reply buffer, it guesses the From and Bcc
> addresses. The client is in a better position to guess these, and this
> patch adjusts notmuch-reply accordingly.
>
> diff --git a/notmuch.el b/notmuch.el
> index
t available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20100311/60264230/attachment.pgp>
On Thu, 11 Mar 2010 14:00:08 +0100, Michal Sojka wrote:
> Hi James,
>
> On Tue, 09 Mar 2010, James Vasile wrote:
> > When notmuch creates a reply buffer, it guesses the From and Bcc
> > addresses. The client is in a better position to guess these, and this
> > patch adjusts notmuch-reply
Hey all,
After standing on the sidelines for several months now, I've finally
transitioned to
using notmuch exclusively. I had originally intended on waiting until the vim
was
in a usable state, but it seems that the emacs client is usable enough for
basic mail reading for the time being. It
Hey all,
While the notmuch command-line interface is fantastic, there defintely are a few
gaps which hurt performance. Since I've been following, I've seen several
threads on how to handle message addition and initial tagging[1][2]. I recall
that some time ago Carl had the idea of applying only a
On Thu, 11 Mar 2010, James Vasile wrote:
> On Thu, 11 Mar 2010 14:00:08 +0100, Michal Sojka
> wrote:
> > Hi James,
> >
> > On Tue, 09 Mar 2010, James Vasile wrote:
> > > When notmuch creates a reply buffer, it guesses the From and Bcc
> > > addresses. The client is in a better position to
On Thu, 11 Mar 2010 17:22:41 +0100, Michal Sojka wrote:
> thanks for clarification. It all sounds reasonable. The only problem I
> can see now is that if I create a new account on my machine and run
> emacs there, then the value of user-mail-address is @
> which doesn't refer to existing mailbox.
Hey all,
Here's a rebased version of my shared library patch. It's pretty similar to the
last version and should build against a clean tree (I'd recommend git clean
-fxd).
Let me know if you have any build issues.
In the eyes of the powers that be, what is the long-term status of this patch?
---
.gitignore |1 +
Makefile |1 +
Makefile.local |9 ++---
lib/Makefile.local | 11 ++-
4 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/.gitignore b/.gitignore
index efa98fb..daf8094 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,6
On Thu, 04 Mar 2010 09:25:45 +0100, "Sebastian Spaeth" wrote:
> I just tried out this patch to compile notmuch as a shared library and
> while producing lib/libnotmuch.so.1 it fails to find notmuch later:
Try the version I just posted. It will apply against master and builds on my
machine.
>
On Thu, 11 Mar 2010, Ben Gamari wrote:
> While the notmuch command-line interface is fantastic, there defintely are a
> few
> gaps which hurt performance. Since I've been following, I've seen several
> threads on how to handle message addition and initial tagging[1][2]. I recall
> that some time
On Thu, 11 Mar 2010 17:52:34 -0500 (EST), David A Benjamin wrote:
> To avoid breaking the current behavior, what if the set of tags applied to
> new/moved/deleted(?) messages could be set on the command line or some
> other library interface, while just perhaps defaulting to unread/inbox?
>
21 matches
Mail list logo
