[notmuch] [PATCH] Refactor notmuch-folder-add to avoid recursion. Allow notmuch-folders to contain folders with empty search criteria.

Refactor notmuch-folder-add to avoid recursion. Allow notmuch-folders to contain folders with empty search criteria. Setting a folder's search criteria to "" in notmuch-folders causes a label to be printed in notmuch-folder view. This is good for helping organizing folders, e.g. by using

[notmuch] patchwork test instance

-- oscar wilde spamtraps: madduck.bogus at madduck.net -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/) URL: <http://notmuchm

[notmuch] loss of duplicate messages

attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/dbdfa481/attachment.pgp>

[notmuch] JSON output as default [was: Re: [PATCH] Add an "--output=(json|text|)" command-line option...]

> > I definitely want to be able to pipe single-field lists coming from > > notmuch to grep, xargs, shell for loops, etc. without having to > decode > > JSON. > > While I would love to see JSON (even by default), I agree. If I just > want to code up a notmuch-based address book with sth like: >

[notmuch] envelope-to

Can notmuch search for envelope-to:? Or for that matter, can it search for arbitrary headers? I get a lot of BCC mail. The envelope-to is a good way for me to know which of my various addresses was BCC'd. Thanks.

[notmuch] JSON output as default [was: Re: [PATCH] Add an "--output=(json|text|)" command-line option...]

> I definitely want to be able to pipe single-field lists coming from > notmuch to grep, xargs, shell for loops, etc. without having to decode > JSON. While I would love to see JSON (even by default), I agree. If I just want to code up a notmuch-based address book with sth like: notmuch show

[notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

t; or making it all configurable. This isn't a bad idea at all. I don't think it changes the functionality much, but it does make things conceptually much simpler, which I'm always in favor of (KIS). jamie. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/f6ad47ab/attachment.pgp>

[notmuch] [PATCH] notmuch.el: hide original message in top posted replies.

From: David Bremner This code treats top posted copies essentially like signatures, except that it doesn't sanity check their length, since neither do their senders. In an unrelated cleanup, remove the let definition of sig-end, since it was unused. New user-visible variable:

[notmuch] [PATCH] Calls to notmuch get queued and executed asynchronously.

Sleep between retrying asynchronous notmuch commands and check for notmuch-process before firing off a new one If the db is locked when notmuch tries to write to it, an error is reported to the client (in this case, notmuch.el). Instead of accepting that error, wait a small amount of time and

[notmuch] [PATCH] Simplify "unread" tag handling in emacs UI.

-- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/c659445a/attachment-0001.pgp>

[notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/7ec5f864/attachment.pgp>

[notmuch] Introducing notmuchsync

ype: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/a622b600/attachment.pgp>

[notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

onth or two) and then deleting them after that (with something like a cron job using a convenient --before="2 months ago" syntax to a notmuch search command). -- 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/20100224/5a4864e5/attachment.pgp>

[notmuch] Git feature branch

http://notmuchmail.org/pipermail/notmuch/attachments/20100224/59f381ce/attachment.pgp>

[notmuch] patchwork test instance

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/20100224/30172a2d/attachment.pgp>

[notmuch] patchwork test instance

teresting. -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/20100224/7a2c0f74/attachment.pgp>

[notmuch] Git feature branch

otmuch/attachments/20100224/84f16445/attachment.pgp>

[notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

to indicate deletion. -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/20100224/1ea81a0f/attachment.pgp>

[notmuch] [PATCH] Support for deletion (patch included)

(string-match-p notmuch-search-disjunctive-regexp > query) (concat "( " query " )") query))) > (notmuch-search (concat notmuch-search-query-string " and " > grouped-query) notmuch-search-oldest-first))) Is this just an accidental chunk in the patch? I d

[notmuch] [PATCH] Simplify "unread" tag handling in emacs UI.

o accept any help. -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/20100224/bed6349a/attachment.pgp>

[notmuch] Introducing notmuchsync

independent of whether the current functionality gets folded into notmuch). -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/20100224/6b59ed94/attachment.pgp>

[notmuch] [PATCH v3] notmuch.el: Refactor citation markup. Variables for minimum size, button text.

org/pipermail/notmuch/attachments/20100224/ee143568/attachment.pgp>

[notmuch] JSON output as default [was: Re: [PATCH] Add an "--output=(json|text|)" command-line option...]

ailable Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20100224/e4ba2422/attachment-0001.pgp>

[notmuch] [PATCH v2] notmuch-query.el: new file to support access to the notmuch database.

From: David Bremner Initially this file provides one main function notmuch-query-get-threads, which takes a set of search terms, and returns a parsed set of matching threads as a lisp data structure. A set of notmuch-query-map-* functions are provided to help map functions over

[notmuch] [PATCH] Rework saving of attachments.

Resending to the list as well as just Carl... {-- Tue, 23 Feb 2010 11:12:36 -0800: Carl wrote: --} Carl> I apologize for the extraordinarly-late review, but here it Carl> is... No problem at all. You're updates on status have been sufficient to convince me you were making progress and

[notmuch] [PATCH v2] notmuch-query.el: new file to support access to the notmuch database.

From: David Bremner brem...@unb.ca Initially this file provides one main function notmuch-query-get-threads, which takes a set of search terms, and returns a parsed set of matching threads as a lisp data structure. A set of notmuch-query-map-* functions are provided to help map functions over

Re: [notmuch] JSON output as default [was: Re: [PATCH] Add an --output=(json|text|) command-line option...]

I definitely want to be able to pipe single-field lists coming from notmuch to grep, xargs, shell for loops, etc. without having to decode JSON. While I would love to see JSON (even by default), I agree. If I just want to code up a notmuch-based address book with sth like: notmuch show

Re: [notmuch] JSON output as default [was: Re: [PATCH] Add an --output=(json|text|) command-line option...]

On Wed, 24 Feb 2010 15:27:18 +0100 (CET), ra...@free.fr wrote: I definitely want to be able to pipe single-field lists coming from notmuch to grep, xargs, shell for loops, etc. without having to decode JSON. While I would love to see JSON (even by default), I agree. If I just

Re: [notmuch] [PATCH] Rework saving of attachments.

Resending to the list as well as just Carl... {-- Tue, 23 Feb 2010 11:12:36 -0800: Carl cwo...@cworth.org wrote: --} Carl I apologize for the extraordinarly-late review, but here it Carl is... No problem at all. You're updates on status have been sufficient to convince me you were making

Re: [notmuch] Introducing notmuchsync

On Mon, 18 Jan 2010 16:12:28 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: - Synchronizes the S flag with the unread tag (1-way). The synchronization direction is decided by using either --sync (change maildir flags according to notmuch) or --revsync (change notmuch

Re: [notmuch] [PATCH] Simplify unread tag handling in emacs UI.

On Wed, 17 Feb 2010 14:33:11 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: On Tue, 19 Jan 2010 17:54:16 -0500, Jameson Rollins jroll...@finestructure.net wrote: This patch is intended to greatly simplify the handling of the unread tag in the emacs UI. This patch adds a new function

[notmuch] [PATCH] notmuch.el: hide original message in top posted replies.

From: David Bremner brem...@unb.ca This code treats top posted copies essentially like signatures, except that it doesn't sanity check their length, since neither do their senders. In an unrelated cleanup, remove the let definition of sig-end, since it was unused. New user-visible variable:

Re: [notmuch] [PATCH] Support for deletion (patch included)

On Sun, 13 Dec 2009 12:54:09 +0100, Matthieu Lemerre ra...@free.fr wrote: I forgot the attachment.. Hi Matthieu, This is a very interesting patch. Thanks for contributing it. Could you also write a commit message describing what the patch does? The easiest way for me to apply that would be if

Re: [notmuch] Introducing notmuchsync

On Wed, 24 Feb 2010 10:19:06 -0800, Carl Worth cwo...@cworth.org wrote: Elsewhere in the thread Jameson Rollins wrote: I should have mentioned in my previous mail that I think this tool is a great idea, and I plan on using it. I just hope that all of it's functionality will be integrated

Re: [notmuch] Git feature branch

On Wed, 27 Jan 2010 14:17:39 -0500, Ben Gamari bgam...@gmail.com wrote: I agree. There is no good reason to switch away from the existing infrastructure. If he wants, Carl can give regular contributors their own repositories on notmuchmail.org if some people have difficulties providing it

Re: [notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

On Wed, 24 Feb 2010 10:53:50 -0800, Carl Worth cwo...@cworth.org wrote: But this patch does have two good ideas not in the other patch, (both of which I mentioned in the review): 1. It adds a keybinding to the notmuch-show mode 2. It removes the inbox and unread tags while adding the tag

Re: [notmuch] Git feature branch

On Wed, 03 Feb 2010 22:58:05 -0500, Jameson Rollins jroll...@finestructure.net wrote: Once the project becomes more mature and other developers are vetting patches, then their branches can take over as master in the absence of an outdated canonical master. The other thing that will happen as

Re: [notmuch] [PATCH] Simplify unread tag handling in emacs UI.

On Wed, 24 Feb 2010 10:26:47 -0800, Carl Worth cwo...@cworth.org wrote: On Wed, 17 Feb 2010 14:33:11 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: On Tue, 19 Jan 2010 17:54:16 -0500, Jameson Rollins jroll...@finestructure.net wrote: This patch is intended to greatly simplify the

Re: [notmuch] [PATCH] Calls to notmuch get queued and executed asynchronously.

Sleep between retrying asynchronous notmuch commands and check for notmuch-process before firing off a new one If the db is locked when notmuch tries to write to it, an error is reported to the client (in this case, notmuch.el). Instead of accepting that error, wait a small amount of time and

Re: [notmuch] [PATCH] add notmuch-show-delete keybinding 'd'

On Wed, 24 Feb 2010 14:01:18 -0500, Jameson Rollins jroll...@finestructure.net wrote: 2. It removes the inbox and unread tags while adding the tag to indicate deletion. Hey, Carl. Why is this last point important? I guess I was imagining the case of running notmuch search tag:inbox at

[notmuch] envelope-to

Can notmuch search for envelope-to:? Or for that matter, can it search for arbitrary headers? I get a lot of BCC mail. The envelope-to is a good way for me to know which of my various addresses was BCC'd. Thanks. ___ notmuch mailing list

Re: [notmuch] patchwork test instance

also sprach Carl Worth cwo...@cworth.org [2010.02.24.2010 +0100]: Carl, would you consider bouncing messages to addresses like patchwork+rejec...@patchwork.notmuchmail.org? That would make it trivial for me to write glue to update patchwork automatically. Now you're talking my language,

Re: [notmuch] [PATCH] Support for deletion (patch included)

Hi Carl, Could you also write a commit message describing what the patch does? The easiest way for me to apply that would be if you would create a git commit, then run git format-patch origin/master and mail the resulting files, (the git send-email command can be used here, or you can insert