[notmuch] Bulk message tagging

2010-04-17 Thread Arian Kuschki
Hi -Original Message- From: Carl Worth Sent: 17 April 2010 17:43 So one could query with sysconf and break things up into multiple commands as needed. Doesn't xargs do exactly this?

[PATCH] configure: Add support for GMime 2.6

2010-04-17 Thread Adrien Bustany
Just sending the patch again for the 0.3 merge window... Cheers Adrien On Thu, 15 Apr 2010 19:41:55 -0400, Adrien Bustany wrote: > Notmuch compiles just fine with GMime 2.6, so accept it in the configure > script. > --- > configure |5 + > 1 files changed, 5 insertions(+), 0

[PATCH v2] Name thread based on matching msgs instead of first msg.

2010-04-17 Thread Jesse Rosenthal
At the moment all threads are named based on the name of the first message in the thread. However, this can cause problems if people either start new threads by replying-all (as unfortunately, many out there do) or change the subject of their mails to reflect a shift in a thread on a list. This

The archive operation should only archive open messages

2010-04-17 Thread Dirk Hohndel
On Sat, 17 Apr 2010 08:28:49 -0700, Carl Worth wrote: > On Thu, 15 Apr 2010 16:59:13 -0400, Jameson Rollins finestructure.net> wrote: > > I actually *really* don't like that the space bar does this. In fact, I > > build my own notmuch-show-advance function in a notmuch-hacks.el that I > > load

[Announce] notmuch release 0.2 now available

2010-04-17 Thread Alex Ghitza
Hi, I'm not sure whether replying to the announcement email is the appropriate way to report building and testing results, but here goes. notmuch-0.2 built fine, but one test failed during 'make test'. I have put the indicated directory up at http://aghitza.org/files/test.16707 with a tarred

[notmuch] Bulk message tagging

2010-04-17 Thread Carl Worth
On Fri, 16 Apr 2010 07:47:45 -0400, Jesse Rosenthal wrote: > I've never run into this error. I usually run into this with things like "rm * */*" or so. > Is there a specific length that triggers > it? If so, we could chunk the tagging command. Or does the max length > depend on the machine and

The archive operation should only archive open messages

2010-04-17 Thread Carl Worth
perations only affect matched messages in the search view, and I agree that this will be extremely convenient. -Carl -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <h

The archive operation should only archive open messages

2010-04-17 Thread Carl Worth
nt folder specification. It's probably simpler to call these "search macros" rather than "saved searches", because that's all the feature really is. -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/20100417/7f6e2328/attachment.pgp>

Re: The archive operation should only archive open messages

2010-04-17 Thread Carl Worth
On Thu, 15 Apr 2010 16:59:13 -0400, Jameson Rollins jroll...@finestructure.net wrote: I actually *really* don't like that the space bar does this. In fact, I build my own notmuch-show-advance function in a notmuch-hacks.el that I load to expressly get around this. Well we definitely do need

Re: The archive operation should only archive open messages

2010-04-17 Thread Carl Worth
On Thu, 15 Apr 2010 17:18:30 -0400, Jesse Rosenthal jrosent...@jhu.edu wrote: Which is all just to say that I think that archiving is just a special case of tagging/untagging, and that the issues raised here should be considered across the larger general case. I do agree that archiving is just

[PATCH v2] Name thread based on matching msgs instead of first msg.

2010-04-17 Thread Jesse Rosenthal
At the moment all threads are named based on the name of the first message in the thread. However, this can cause problems if people either start new threads by replying-all (as unfortunately, many out there do) or change the subject of their mails to reflect a shift in a thread on a list. This