[notmuch] automatically assigning tags to new messages?

Dear notmuch crowd, I heard about notmuch mail a few days ago and I started playing with it. So far, it makes me very happy, but there are some things that I need to learn how to do. I'll start with the most important one: tagging incoming messages automatically. What is the recommended way

Re: [notmuch] automatically assigning tags to new messages?

On Fri, 18 Dec 2009 22:21:54 +1100, Alex Ghitza aghi...@gmail.com wrote: I heard about notmuch mail a few days ago and I started playing with it. So far, it makes me very happy, but there are some things that I need to learn how to do. I'll start with the most important one: tagging incoming

Re: [notmuch] [PATCH] JSON output for notmuch-search and notmuch-show.

On Thu, 17 Dec 2009 21:33:54 -0800, Scott Robinson sc...@quadhome.com wrote: I took an earlier suggestion and didn't use cJSON, instead writing custom code for emitting the new format. Nice! I have a few comments below. Added an --output=(json|text|) command-line option to both

Re: [notmuch] [PATCH] Add an --output=(json|text|) command-line option to both notmuch-search and notmuch-show.

On Fri, 18 Dec 2009 08:59:55 -0400, da...@tethera.net wrote: It took me a little work to apply Scott's patch, so rather than asking him to resend it from git-send-email, I am just sending. I hope no-one is offended (much). I think that's great! Collaboration is what this is all about. I'm

Re: [notmuch] Rather simple optimization for notmuch tag

On Fri, 18 Dec 2009 00:49:00 -0700, Mark Anderson markr.ander...@amd.com wrote: I was updating my poll script that tags messages, and a common idiom is to put tag +mytag search_terms and not tag:mytag I don't know anything about efficiency, but for the simple single-tag case, couldn't we

Re: [notmuch] Missing messages breaking threads

On Fri, 18 Dec 2009 19:53:13 +, James Westby jw+deb...@jameswestby.net wrote: Or do we not index whatever dummy text we add? Or do we not even put it in? Or not even show it at all? I was just thinking of having Missing messages... showing up as the start of the thread, but maybe it's no

[notmuch] [PATCH] Store the size of the file for each message

When indexing a message store the filesize along with it so that when we store all the filenames for a message-id we can know if any of them have different content cheaply. The value stored is defined to be the largest filesize of any of the files for that message. This changes the API for

Re: [notmuch] Missing messages breaking threads

On Fri, 18 Dec 2009 12:52:58 -0800, Carl Worth cwo...@cworth.org wrote: On Fri, 18 Dec 2009 19:53:13 +, James Westby jw+deb...@jameswestby.net wrote: Oh, I was assuming you wouldn't index any text. The UI can add missing message for a document with no filename, for example. Works for me.

Re: [notmuch] [PATCH] Store the size of the file for each message

On Fri, 18 Dec 2009 21:21:03 +, James Westby jw+deb...@jameswestby.net wrote: Here's the first part, storing the filesize. I'm using add_value so that we can make it sortable, is that valid for retrieving it as well? Yes, a value makes sense here and should make the value easy to

[notmuch] wish: more informative citations

Wouldn't it be nice if citations showed the first line or so of the text being cited? Stealing text from another thread, In case of a citation following immediately new contents. When the citation was collapsed: [1-line citation. Click/Enter to show.] Lorem ipsum dolor sit amet,

[notmuch] [PATCH] Reindex larger files that duplicate ids we have

When we see a message where we already have the file id stored, check if the size is larger. If it is then re-index and set the file size and name to be the new message. --- Here's the (quite simple) patch to implement indexing the largest copy of each mail that we have. Does the

Re: [notmuch] [PATCH] Store the size of the file for each message

On Fri, 18 Dec 2009 16:57:16 -0800, Carl Worth cwo...@cworth.org wrote: You can, actually. Just set the NOTMUCH_CONFIG environment variable to your alternate configuration file. (And yes, we're missing any mention of this in our documentation.) Sweet. Where would be the best place to document

[notmuch] [PATCH] Fix-up some outdated comments.

--- lib/message.cc |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/message.cc b/lib/message.cc index cc32741..7129d59 100644 --- a/lib/message.cc +++ b/lib/message.cc @@ -391,7 +391,7 @@ notmuch_message_get_replies (notmuch_message_t *message) * multiple

[notmuch] keeping a copy of sent mail locally

Hello, Many thanks to Marten and Carl for the advice on using scripts for assigning tags automatically. It works like a charm. The next hurdle seems to be dealing with sent mail. I would like each message that I send to be saved in my local mail folder and treated the same as all my other

[notmuch] automatically assigning tags to new messages?

Dear notmuch crowd, I heard about notmuch mail a few days ago and I started playing with it. So far, it makes me very happy, but there are some things that I need to learn how to do. I'll start with the most important one: tagging incoming messages automatically. What is the recommended way

[notmuch] automatically assigning tags to new messages?

On Fri, 18 Dec 2009 22:21:54 +1100, Alex Ghitza wrote: > I heard about notmuch mail a few days ago and I started playing with > it. So far, it makes me very happy, but there are some things that I > need to learn how to do. I'll start with the most important one: > tagging incoming messages

[notmuch] [PATCH] Add an "--output=(json|text|)" command-line option to both notmuch-search and notmuch-show.

From: Scott Robinson In the case of notmuch-show, "--output=json" also implies "--entire-thread" as the thread structure is implicit in the emitted document tree. As a coincidence to the implementation, multipart message ID numbers are now incremented with each part printed.

[notmuch] [PATCH] Add an "--output=(json|text|)" command-line option to both notmuch-search and notmuch-show.

. Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20091218/55d68a46/attachment.pgp>

[notmuch] Rather simple optimization for notmuch tag

evel optimization to be in place. -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/attachments/20091218/00565d5b/attachment.pgp>

[notmuch] automatically assigning tags to new messages?

s on every message that the display is often just a lot of noise). Anyway, that's something I plan to experiment with. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <htt

[notmuch] First attempt to add smart completion in notmuch-search

-- 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/attachments/20091218/a322e374/attachment.pgp>

[notmuch] [PATCH] Add an "--output=(json|text|)" command-line option to both notmuch-search and notmuch-show.

Excerpts from Carl Worth's message of Fri Dec 18 09:33:43 -0800 2009: > On Fri, 18 Dec 2009 08:59:55 -0400, david at tethera.net wrote: > > It took me a little work to apply Scott's patch, so rather than asking > > him to resend it from git-send-email, I am just sending. I hope no-one > > is

[notmuch] [PATCH] JSON output for notmuch-search and notmuch-show.

Excerpts from Carl Worth's message of Fri Dec 18 09:31:39 -0800 2009: > [...] > I don't know why, but I think I'd prefer --format for the name here. ACK > [...] > It looks like the new documentation is missing that point, (and the man > page in notmuch.1 is missing an update as well). ACK >

[notmuch] Missing messages breaking threads

that. -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/attachments/20091218/5cda441f/attachment.pgp>

[notmuch] Missing messages breaking threads

On Fri, 18 Dec 2009 11:41:18 -0800, Carl Worth wrote: > On Fri, 18 Dec 2009 19:02:21 +, James Westby jameswestby.net> wrote: > > Therefore I'd like to fix this. The obvious way is to > > introduce documents in to the db for each id we see, and > > threading should then

[notmuch] Missing messages breaking threads

on-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20091218/185328f8/attachment.pgp>

[notmuch] [PATCH] Store the size of the file for each message

When indexing a message store the filesize along with it so that when we store all the filenames for a message-id we can know if any of them have different content cheaply. The value stored is defined to be the largest filesize of any of the files for that message. This changes the API for

[notmuch] Missing messages breaking threads

On Fri, 18 Dec 2009 12:52:58 -0800, Carl Worth wrote: > On Fri, 18 Dec 2009 19:53:13 +, James Westby jameswestby.net> wrote: > Oh, I was assuming you wouldn't index any text. The UI can add "missing > message" for a document with no filename, for example. Works for me. > >

[notmuch] [PATCH] Store the size of the file for each message

xt attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20091218/8d9da30f/attachment.pgp>

[notmuch] [PATCH] Add an "--output=(json|text|)" command-line option to both notmuch-search and notmuch-show.

On Fri, 18 Dec 2009 09:33:43 -0800, Carl Worth wrote: > I think that selecting *what* to emit is orthogonal from selecting *how* > to format that output. I can see that point of view. > See some ideas in the TODO file, (where I proposed --for and --format > options for these). It's a detail,

[notmuch] wish: more informative citations

Wouldn't it be nice if citations showed the first line or so of the text being cited? Stealing text from another thread, > In case of a citation following immediately new contents. When the citation > was collapsed: > > [1-line citation. Click/Enter to show.] > Lorem ipsum dolor sit

[notmuch] [PATCH] Store the size of the file for each message

on-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20091218/b5785db1/attachment.pgp>

[notmuch] wish: more informative citations

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/attachments/20091218/0ce61e8b/attachment.pgp>

[notmuch] [PATCH] Store the size of the file for each message

RL: <http://notmuchmail.org/pipermail/notmuch/attachments/20091218/3cae398e/attachment-0001.pgp>