Distributed Notmuch

Hi guys, It's kind of academic for me right now because I'm mostly just using one computer, but one reason I've hesitated to switch over entirely to notmuch is that it's hard to distribute across many machines. The last time I wrote the list about this, David Bremner pointed me to gitmuch in

Re: [PATCH 1/2] clean up compare thread ids python test

On Mon, 2 Jan 2012 14:51:26 +, Patrick Totzke patricktot...@googlemail.com wrote: This makes the test script open the database in READ_ONLY mode and use the libraries own sorting methods instead of sort. +1 I don't want to fudge the tests (I don't know a thing about them), so I can't

Re: [PATCH 1/4] Add the option --reply-to to notmuch reply.

On Fri, 6 Jan 2012 13:34:14 +, Mark Walters markwalters1...@gmail.com wrote: Possible values for this option are sender which replies just to sender and all (the default). More precisely reply to sender follows these rules: reply only to sender unless it was the user

Re: [PATCH 2/2] python test compare message ids

On Mon, 2 Jan 2012 14:51:27 +, Patrick Totzke patricktot...@googlemail.com wrote: Introduces a second (trivial) test for the python bindings that searches for message ids and compares the output with that of `notmuch search`. Test passes, so it went in. pgpOPxhSYny4e.pgp Description:

notmuch git's disk is full! ERROR pushing.

Actually trying to push the above 2 patches, I get Writing objects: 100% (8/8), 1.25 KiB, done. Total 8 (delta 5), reused 0 (delta 0) error: unable to create temporary sha1 filename : No space left on device fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To

Re: Info about notmuch database

On Thu, 05 Jan 2012 16:04:22 +0100, Thomas Jost schno...@schnouki.net wrote: There's a description of the DB schema in lib/database.cc in the notmuch source code. But you may also consider just using libnotmuch instead, if that's enough for what you want to do. Also: why Xapian? I'm already

Re: [PATCH 5/7] py3k: the basestring and unicode types are removed in python 3

Hi Tomi, Hi Sebastian :) Quoting Tomi Ollila (2012-01-04 19:07:11) On Mon, 02 Jan 2012 16:15:58 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: Happy new year. Pushed patches 1-4 of this series so far. Looking fine, nice, thanks. but ugh, the below seems like a rather ugly hack in a

[PATCH] py3k: the basestring and unicode types are removed in python 3

--- bindings/python/notmuch/globals.py | 34 ++ 1 files changed, 22 insertions(+), 12 deletions(-) diff --git a/bindings/python/notmuch/globals.py b/bindings/python/notmuch/globals.py index 32ed9ae..4138460 100644 --- a/bindings/python/notmuch/globals.py +++

Re: Info about notmuch database

On Sun, 08 Jan 2012 13:59:30 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: On Thu, 05 Jan 2012 16:04:22 +0100, Thomas Jost schno...@schnouki.net wrote: There's a description of the DB schema in lib/database.cc in the notmuch source code. But you may also consider just using libnotmuch

Re: [PATCH 1/4] Add the option --reply-to to notmuch reply.

On Sun, 08 Jan 2012 14:47:33 +0200, Jani Nikula j...@nikula.org wrote: + /* We add the addresses if we are replying to all or we have not yet found +* a non-user address. We have to keep parsing to make sure we do find the +* correct from address for the user, but we pass a

Re: [PATCH 1/4] Add the option --reply-to to notmuch reply.

On Sun, 08 Jan 2012 15:08:20 +, Mark Walters markwalters1...@gmail.com wrote: I think replying to an email which we sent and which does not have any other person on the to: line is sufficiently rare that it doesn't really matter what we do in this case. I ended up fixing all of this

Re: Python bindings for adoption

Hi Sebastian, hi everyone :) Quoting Sebastian Spaeth (2012-01-02 17:14:58) Hi all, a happy new year! After a few weeks of notmuch abstinence I am being overwhelmed with 750 new notmuch mails, and I really don't have the time or will (nor does my family approve) to spend enormous amounts of time

Re: nmbug changes

Hey David, Quoting David Bremner (2011-12-23 22:56:31) For those of you following/using the nmbug experiment, I made some slightly disruptive changes, in order to support auto-updating the web view on push. I'm having trouble with nmbug, I did follow the instructions in this mail and in the

[PATCH 4/4 v2] emacs: use pop-at-end functionality in archive/delete-message functions

This provides a smoother message processing flow by reducing the number of key presses needed for these common operations. --- Sorry, there were some errant extra parens at the end of these function definitions. emacs/notmuch-show.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

[PATCH 1/4 v2] emacs: add show-mode functions to archive/delete only current message

This adds two new function, notmuch-show-{archive,delete}-message, that archive/delete the current message, and then move to the next open one. --- Sorry, there were some errant extra parens at the end of these function definitions. emacs/notmuch-show.el | 24 1 files

[PATCH 4/4 v3] emacs: use pop-at-end functionality in archive/delete-message functions

This provides a smoother message processing flow by reducing the number of key presses needed for these common operations. --- Sorry sorry. I originally missed the problem in patch 1/4, so I had to modify this patch again to apply against the new version of the previous. So sorry for the noise,

[PATCH] man: add missing SEE ALSO header to notmuch reply man page

Signed-off-by: Jani Nikula j...@nikula.org --- man/man1/notmuch-reply.1 |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1 index 099d808..db464d8 100644 --- a/man/man1/notmuch-reply.1 +++ b/man/man1/notmuch-reply.1 @@

[PATCH v2 0/6] reply to sender

Hi all, here's v2 of the reply-to-sender series. Patches 1 2 are exactly the same as before. Changes since first version: - Patch 3: Settle on --reply-to=(all|sender) option for notmuch reply. This was originally Carl Worth's suggestion, predates this patch set, and, as you'd expect, is in

[PATCH v2 2/6] cli: convert notmuch reply to use the new argument parser

Use the new notmuch argument parser to handle arguments in notmuch reply. There should be no functional changes. Signed-off-by: Jani Nikula j...@nikula.org --- notmuch-reply.c | 75 +++ 1 files changed, 37 insertions(+), 38 deletions(-) diff

[PATCH v2 3/6] cli: add support for replying just to the sender in notmuch reply

Add new option --reply-to=(all|sender) to notmuch reply to select whether to reply to all (sender and all recipients), or just sender. Reply to all remains the default. Credits to Mark Walters markwalters1...@gmail.com for his similar earlier work where I picked up the basic idea of handling

[PATCH v2 4/6] emacs: add support for replying just to the sender

Provide reply to sender counterparts to the search and show reply functions. Add key binding 'R' to reply to sender, while keeping 'r' as reply to all, both in search and show views. Signed-off-by: Jani Nikula j...@nikula.org --- emacs/notmuch-mua.el |9 ++--- emacs/notmuch-show.el |

[PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

Change the default reply key bindings, making 'r' reply-to-sender and 'R' reply-to-all. Signed-off-by: Jani Nikula j...@nikula.org --- It seemed to me that most people wanted this, and nobody spoke for keeping the old binding now that we have reply-to-sender. This as a separate patch so it's

Re: [PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

On Sun, Jan 8, 2012 at 14:48, Jani Nikula j...@nikula.org wrote: It seemed to me that most people wanted this, and nobody spoke for keeping the old binding now that we have reply-to-sender. This as a separate patch so it's easy to drop if needed. FWIW, I generally prefer reply-all as the

Re: nmbug changes

On Sun, 08 Jan 2012 16:24:06 -, Justus Winter 4win...@informatik.uni-hamburg.de wrote: I'm having trouble with nmbug, I did follow the instructions in this mail and in the wiki, but nmbug never adds tags to my notmuch database (it is supposed to do that, right?). In case you just want to

Re: Python bindings for adoption

On Sun, 08 Jan 2012 16:16:06 -, Justus Winter 4win...@informatik.uni-hamburg.de wrote: I've decided to step up as a new maintainer for the libnotmuch python bindings. I assume that I'll have to mail an ssh public key to someone for repository access, right? That's right. Carl (in

Re: [PATCH v2 3/6] cli: add support for replying just to the sender in notmuch reply

I like this version (of the whole series) but have two queries. (Note I haven't actually tried it out yet: I have just been reading the code.) + /* Force recipient type in reply-to-sender mode just in case replying to + * user's own message finds recipients in Cc/Bcc fields only. +

Re: [PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

On Sun, 8 Jan 2012 15:01:30 -0700, Jeremy Nickurak not-m...@trk.nickurak.ca wrote: FWIW, I generally prefer reply-all as the default. In my experience, when a message is sent to a bunch of people, it's usually treated as a forum discussion where everybody wants to be in on everything. Also,

Re: [PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

On Sun, Jan 8, 2012 at 16:32, Jameson Graef Rollins jroll...@finestructure.net wrote: That's a good point.  I think that maybe people are wanting to protect against the accidental reply to all when you only mean to reply to the sender. Certainly a worthy cause. All I'm saying is I make the

Re: [PATCH] emacs: call notmuch tag only once when archiving a thread

On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula j...@nikula.org wrote: [...] In the show view it only modifies the messages that are currently visible. This is to make sure you don't accidentally archive things that have arrived after refreshing the buffer. I think this is safest. Hmm.

Re: [PATCH 2/4] emacs: repurpose notmuch-show-archive-thread-internal function for general thread tagging

Jameson, Some comments below: On Sat, 7 Jan 2012 14:28:12 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: Instead of having a function that is only used for archiving a thread, we instead make it useful for any tagging operation. The new function,

Re: [PATCH 2/4] emacs: add option to notmuch-show-next-open-message to pop out to parent buffer if at end

Jameson, One small, stylistic/nitpicky comment :) On Sat, 7 Jan 2012 17:26:53 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: This will allow for keybindings that achieve a smoother message processing flow by reducing the number of key presses needed for most common

Re: [PATCH] emacs: call notmuch tag only once when archiving a thread

Quoth Aaron Ecay on Jan 08 at 7:56 pm: On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula j...@nikula.org wrote: [...] In the show view it only modifies the messages that are currently visible. This is to make sure you don't accidentally archive things that have arrived after refreshing

Re: [PATCH 1/4] emacs: new customization variable to exclude deleted messages from search

Jameson, One comment On Sat, 7 Jan 2012 14:28:11 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: The new customization variable, notmuch-search-exclude-deleted, when set to t, will exclude any messages with the deleted tag from searches. Additionally, specifying

Re: [PATCH 4/4] emacs: Use the new JSON reply format.

Adam, One comment below. On Sun, 8 Jan 2012 00:52:42 -0700, Adam Wolfe Gordon awg+notm...@xvx.ca wrote: From: Adam Wolfe Gordon a...@xvx.ca Using the new JSON reply format allows emacs to quote HTML parts nicely by first parsing them with w3m, then quoting them. This is very useful for

Re: [PATCH 0/4] Quoting HTML-only emails in replies redux

On Sun, 8 Jan 2012 00:52:38 -0700, Adam Wolfe Gordon awg+notm...@xvx.ca wrote: [...] There should probably be some customize variables for this in emacs, to control (for example) whether to quote HTML parts and whether to prefer HTML or plaintext parts for quoting. Any suggestions for

Re: [PATCH 1/4] emacs: new customization variable to exclude deleted messages from search

@@ -927,6 +932,9 @@ The optional parameters are used as follows: (set 'notmuch-search-target-thread target-thread) (set 'notmuch-search-target-line target-line) (set 'notmuch-search-continuation continuation) +(when (and notmuch-search-exclude-deleted + (not

Re: [PATCH 1/4] emacs: new customization variable to exclude deleted messages from search

On Sun, 8 Jan 2012 20:49:38 -0500, Austin Clements amdra...@mit.edu wrote: @@ -927,6 +932,9 @@ The optional parameters are used as follows: (set 'notmuch-search-target-thread target-thread) (set 'notmuch-search-target-line target-line) (set 'notmuch-search-continuation

Re: [PATCH 1/4] emacs: new customization variable to exclude deleted messages from search

Quoth Jameson Graef Rollins on Jan 08 at 6:34 pm: On Sun, 8 Jan 2012 20:49:38 -0500, Austin Clements amdra...@mit.edu wrote: @@ -927,6 +932,9 @@ The optional parameters are used as follows: (set 'notmuch-search-target-thread target-thread) (set 'notmuch-search-target-line

Re: [PATCH 2/4] emacs: repurpose notmuch-show-archive-thread-internal function for general thread tagging

Thanks so much for the review, Aaron. On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay aarone...@gmail.com wrote: A couple of comments on the arguments: - It would be good to make show-next optional. This will enable code to call the fn with only two arguments, and not showing next will be

Re: [PATCH 1/4] emacs: new customization variable to exclude deleted messages from search

Quoth myself on Jan 08 at 8:49 pm: @@ -927,6 +932,9 @@ The optional parameters are used as follows: (set 'notmuch-search-target-thread target-thread) (set 'notmuch-search-target-line target-line) (set 'notmuch-search-continuation continuation) +(when (and

Re: [PATCH 2/4] emacs: repurpose notmuch-show-archive-thread-internal function for general thread tagging

On Sun, 08 Jan 2012 18:49:56 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: Thanks so much for the review, Aaron. On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay aarone...@gmail.com wrote: A couple of comments on the arguments: - It would be good to make show-next optional.

Re: notmuch git's disk is full! ERROR pushing.

On Sun, 08 Jan 2012 13:55:53 +0100, Sebastian Spaeth sebast...@sspaeth.de wrote: Actually trying to push the above 2 patches, I get Writing objects: 100% (8/8), 1.25 KiB, done. Total 8 (delta 5), reused 0 (delta 0) error: unable to create temporary sha1 filename : No space left on device

[RFC PATCH 0/9] -std=c99 / -std=c++0x -pedantic

Hi all, this series was borne of curiousity about compiling the notmuch codebase using -std=c99 / -std=c++0x -pedantic options. The C part is split into separate patches to make it easier to see each warning and fix; with C++ I didn't bother so much. Turns out there are a few specific issues, but

[RFC PATCH 1/9] build: use -std=c99 -pedantic for C source

Signed-off-by: Jani Nikula --- configure |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/configure b/configure index e90b76f..f84262d 100755 --- a/configure +++ b/configure @@ -25,8 +25,8 @@ fi # environment variables) CC=${CC:-gcc} CXX=${CXX:-g++}

[RFC PATCH 2/9] xutil: #define _POSIX_C_SOURCE to get strdup()

strdup() is not standard C99. #define _POSIX_C_SOURCE 200809L to use it. This fixes -std=c99 -pedantic warning: util/xutil.c: In function ?xstrdup?: util/xutil.c:74:5: warning: implicit declaration of function ?strdup? [-Wimplicit-function-declaration] util/xutil.c:74:9: warning: assignment

[RFC PATCH 4/9] lib: HACK: avoid warnings from talloc_steal()

talloc.h #defines talloc_steal() with macros to make it type safe, but introduces a warning when compiled using -std=c99 -pedantic: lib/tags.c: In function ?_notmuch_tags_create?: lib/tags.c:43:5: warning: ISO C forbids braced-groups within expressions [-pedantic] Call _talloc_steal_loc()

[RFC PATCH 3/9] lib: fix messages.c build warn

lib/messages.c: In function ?notmuch_messages_move_to_next?: lib/messages.c:131:2: warning: ISO C forbids ?return? with expression, in function returning void [-pedantic] Signed-off-by: Jani Nikula --- lib/messages.c |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git

[RFC PATCH 5/9] cli: fix warning about variadic macros

notmuch-restore.c: In function ?notmuch_restore_command?: notmuch-restore.c:87:54: warning: ISO C99 requires rest arguments to be used [enabled by default] and elsewhere. ##__VA_ARGS__ is a GCC CPP extension. Signed-off-by: Jani Nikula --- notmuch-client.h |9 ++--- 1 files changed, 6

[RFC PATCH 6/9] cli: fix another warning about variadic macros

notmuch-setup.c: In function ?notmuch_setup_command?: notmuch-setup.c:144:62: warning: ISO C99 requires rest arguments to be used [enabled by default] notmuch-setup.c:174:18: warning: ISO C99 requires rest arguments to be used [enabled by default] Signed-off-by: Jani Nikula ---

[RFC PATCH 7/9] util: fix warning about variadic macros

lib/string-list.c: In function ?_notmuch_string_list_sort?: lib/string-list.c:81:59: warning: ISO C99 requires rest arguments to be used [enabled by default] lib/message-file.c: In function ?notmuch_message_file_restrict_headersv?: lib/message-file.c:147:90: warning: ISO C99 requires rest

[RFC PATCH 9/9] test: smtp-dummy: fixes for -std=c99 -pedantic

Signed-off-by: Jani Nikula --- test/smtp-dummy.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/test/smtp-dummy.c b/test/smtp-dummy.c index 3801a5e..1c29a7d 100644 --- a/test/smtp-dummy.c +++ b/test/smtp-dummy.c @@ -33,6 +33,8 @@ * have been warned. */ +#define

[RFC PATCH 8/9] lib: use -std=c++0x -pedantic

Introduces warnings such as: In file included from /usr/include/gmime-2.4/gmime/gmime.h:39:0, from lib/database.cc:31: /usr/include/gmime-2.4/gmime/gmime-message.h:57:26: warning: comma at end of enumerator list [-pedantic] Signed-off-by: Jani Nikula --- configure

[PATCH 0/4] Quoting HTML-only emails in replies redux

From: Adam Wolfe Gordon Hi everyone, This is a rework of my previous patch series adding support for replying to HTML email in the emacs interface (id:1322671241-23438-1-git-send-email-awg+notmuch at xvx.ca). It was suggested on IRC that a more general solution would be to add a

[PATCH 1/4] test: Add broken test for the new JSON reply format.

From: Adam Wolfe Gordon --- test/multipart |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/test/multipart b/test/multipart index f83526b..f5ebf04 100755 --- a/test/multipart +++ b/test/multipart @@ -589,6 +589,13 @@ Non-text part: text/html EOF

[PATCH 3/4] man: Update notmuch-reply man page for JSON format.

From: Adam Wolfe Gordon --- man/man1/notmuch-reply.1 |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1 index 099d808..240dfed 100644 --- a/man/man1/notmuch-reply.1 +++ b/man/man1/notmuch-reply.1 @@ -41,6

[PATCH 2/4] reply: Add a JSON reply format.

From: Adam Wolfe Gordon This new JSON format for replies includes headers generated for a reply message as well as the headers and all text parts of the original message. Using this data, a client can intelligently create a reply. For example, the emacs client will be able to create

[PATCH 4/4] emacs: Use the new JSON reply format.

From: Adam Wolfe Gordon Using the new JSON reply format allows emacs to quote HTML parts nicely by first parsing them with w3m, then quoting them. This is very useful for users who regularly receive HTML-only email. The behavior for messages that contain plain text parts should be

Distributed Notmuch

Hi guys, It's kind of academic for me right now because I'm mostly just using one computer, but one reason I've hesitated to switch over entirely to notmuch is that it's hard to distribute across many machines. The last time I wrote the list about this, David Bremner pointed me to gitmuch in

[PATCH 1/2] clean up "compare thread ids" python test

notmuch/attachments/20120108/650448f0/attachment-0001.pgp>

[PATCH 1/4] Add the option "--reply-to" to notmuch reply.

On Fri, 6 Jan 2012 13:34:14 +, Mark Walters wrote: > Possible values for this option are "sender" which replies just to > sender and "all" (the default). > > More precisely reply to sender follows these rules: > reply only to sender unless it was the user > reply only

[PATCH 2/2] python test "compare message ids"

non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/4b63d90c/attachment.pgp>

notmuch git's disk is full! ERROR pushing.

ype: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/5efd3a93/attachment.pgp>

Info about notmuch database

Sebastian -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/0d4bfb23/attachment.pgp>

[PATCH 5/7] py3k: the basestring and unicode types are removed in python 3

Hi Tomi, Hi Sebastian :) Quoting Tomi Ollila (2012-01-04 19:07:11) >On Mon, 02 Jan 2012 16:15:58 +0100, Sebastian Spaeth >wrote: >> Happy new year. Pushed patches 1-4 of this series so far. Looking fine, nice, thanks. >> but ugh, the below seems like a rather ugly hack in a function that is

[PATCH] py3k: the basestring and unicode types are removed in python 3

--- bindings/python/notmuch/globals.py | 34 ++ 1 files changed, 22 insertions(+), 12 deletions(-) diff --git a/bindings/python/notmuch/globals.py b/bindings/python/notmuch/globals.py index 32ed9ae..4138460 100644 --- a/bindings/python/notmuch/globals.py +++

Info about notmuch database

next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/4a45b952/attachment.pgp>

[PATCH 1/4] Add the option "--reply-to" to notmuch reply.

On Sun, 08 Jan 2012 14:47:33 +0200, Jani Nikula wrote: > > + /* We add the addresses if we are replying to all or we have not yet > > found > > +* a non-user address. We have to keep parsing to make sure we do find > > the > > +* correct from address for the user, but we pass a NULL

[PATCH 1/4] Add the option "--reply-to" to notmuch reply.

On Sun, 08 Jan 2012 15:08:20 +, Mark Walters wrote: > I think replying to an email which we sent and which does not have any > other person on the to: line is sufficiently rare that it doesn't really > matter what we do in this case. I ended up fixing all of this properly. I'm hoping to

Python bindings for adoption

Hi Sebastian, hi everyone :) Quoting Sebastian Spaeth (2012-01-02 17:14:58) >Hi all, a happy new year! > >After a few weeks of notmuch abstinence I am being overwhelmed with 750 >new notmuch mails, and I really don't have the time or will (nor does my >family approve) to spend enormous amounts of

nmbug changes

Hey David, Quoting David Bremner (2011-12-23 22:56:31) >For those of you following/using the nmbug experiment, I made some >slightly disruptive changes, in order to support auto-updating the web >view on push. I'm having trouble with nmbug, I did follow the instructions in this mail and in the

[PATCH 4/4 v2] emacs: use pop-at-end functionality in archive/delete-message functions

This provides a smoother message processing flow by reducing the number of key presses needed for these common operations. --- Sorry, there were some errant extra parens at the end of these function definitions. emacs/notmuch-show.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

[PATCH 1/4 v2] emacs: add show-mode functions to archive/delete only current message

This adds two new function, notmuch-show-{archive,delete}-message, that archive/delete the current message, and then move to the next open one. --- Sorry, there were some errant extra parens at the end of these function definitions. emacs/notmuch-show.el | 24 1 files

[PATCH 4/4 v3] emacs: use pop-at-end functionality in archive/delete-message functions

This provides a smoother message processing flow by reducing the number of key presses needed for these common operations. --- Sorry sorry. I originally missed the problem in patch 1/4, so I had to modify this patch again to apply against the new version of the previous. So sorry for the noise,

[PATCH] man: add missing SEE ALSO header to notmuch reply man page

Signed-off-by: Jani Nikula --- man/man1/notmuch-reply.1 |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/man/man1/notmuch-reply.1 b/man/man1/notmuch-reply.1 index 099d808..db464d8 100644 --- a/man/man1/notmuch-reply.1 +++ b/man/man1/notmuch-reply.1 @@ -58,6 +58,9 @@

[PATCH v2 0/6] reply to sender

Hi all, here's v2 of the reply-to-sender series. Patches 1 & 2 are exactly the same as before. Changes since first version: - Patch 3: Settle on --reply-to=(all|sender) option for "notmuch reply". This was originally Carl Worth's suggestion, predates this patch set, and, as you'd expect, is

[PATCH v2 1/6] cli: fix use of uninitialized variable in "notmuch reply"

notmuch_show_params_t params is only initialized partially in notmuch_reply_command(). The only field that is used uninitialized is params.decrypt. It is usually non-zero, making "notmuch reply" on encrypted messages work by coincidence. Initialize params properly, and set params.decrypt as

[PATCH v2 2/6] cli: convert "notmuch reply" to use the new argument parser

Use the new notmuch argument parser to handle arguments in "notmuch reply". There should be no functional changes. Signed-off-by: Jani Nikula --- notmuch-reply.c | 75 +++ 1 files changed, 37 insertions(+), 38 deletions(-) diff --git

[PATCH v2 3/6] cli: add support for replying just to the sender in "notmuch reply"

Add new option --reply-to=(all|sender) to "notmuch reply" to select whether to reply to all (sender and all recipients), or just sender. Reply to all remains the default. Credits to Mark Walters for his similar earlier work where I picked up the basic idea of handling reply-to-sender in

[PATCH v2 4/6] emacs: add support for replying just to the sender

Provide reply to sender counterparts to the search and show reply functions. Add key binding 'R' to reply to sender, while keeping 'r' as reply to all, both in search and show views. Signed-off-by: Jani Nikula --- emacs/notmuch-mua.el |9 ++--- emacs/notmuch-show.el | 10 --

[PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

Change the default reply key bindings, making 'r' reply-to-sender and 'R' reply-to-all. Signed-off-by: Jani Nikula --- It seemed to me that most people wanted this, and nobody spoke for keeping the old binding now that we have reply-to-sender. This as a separate patch so it's easy to drop if

[PATCH v2 6/6] test: add tests for "notmuch reply" --reply-to=sender

From: Mark Walters --- This is Mark's work; just a one line change by Jani to take into account a minor change in replying to one's own message. --- test/notmuch-test|1 + test/reply-to-sender | 209 ++ 2 files

[PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

On Sun, Jan 8, 2012 at 14:48, Jani Nikula wrote: > It seemed to me that most people wanted this, and nobody spoke for keeping > the old binding now that we have reply-to-sender. This as a separate patch > so it's easy to drop if needed. FWIW, I generally prefer reply-all as the default. In my

nmbug changes

On Sun, 08 Jan 2012 16:24:06 -, Justus Winter <4winter at informatik.uni-hamburg.de> wrote: > I'm having trouble with nmbug, I did follow the instructions in this > mail and in the wiki, but nmbug never adds tags to my notmuch database > (it is supposed to do that, right?). In case you just

Python bindings for adoption

On Sun, 08 Jan 2012 16:16:06 -, Justus Winter <4winter at informatik.uni-hamburg.de> wrote: > > I've decided to step up as a new maintainer for the libnotmuch python > bindings. I assume that I'll have to mail an ssh public key to someone > for repository access, right? > That's right.

[PATCH v2 3/6] cli: add support for replying just to the sender in "notmuch reply"

I like this version (of the whole series) but have two queries. (Note I haven't actually tried it out yet: I have just been reading the code.) > + /* Force recipient type in reply-to-sender mode just in case replying to > + * user's own message finds recipients in Cc/Bcc fields only. >

[PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

mean to reply to the sender. 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/20120108/5e326084/attachment.pgp>

[PATCH v2 5/6] emacs: bind 'r' to reply-to-sender and 'R' to reply-to-all

On Sun, Jan 8, 2012 at 16:32, Jameson Graef Rollins wrote: > That's a good point. ?I think that maybe people are wanting to protect > against the accidental reply to all when you only mean to reply to the > sender. Certainly a worthy cause. All I'm saying is I make the mistake in the other

[PATCH] emacs: call "notmuch tag" only once when archiving a thread

On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula wrote: [...] > In the show view it only modifies the messages that are currently > visible. This is to make sure you don't accidentally archive things that > have arrived after refreshing the buffer. I think this is safest. Hmm. Perhaps it would

[PATCH 2/4] emacs: repurpose notmuch-show-archive-thread-internal function for general thread tagging

Jameson, Some comments below: On Sat, 7 Jan 2012 14:28:12 -0800, Jameson Graef Rollins wrote: > Instead of having a function that is only used for archiving a thread, > we instead make it useful for any tagging operation. The new > function, notmuch-show-tag-thread-internal, now takes two

[PATCH 2/4] emacs: add option to notmuch-show-next-open-message to pop out to parent buffer if at end

Jameson, One small, stylistic/nitpicky comment :) On Sat, 7 Jan 2012 17:26:53 -0800, Jameson Graef Rollins wrote: > This will allow for keybindings that achieve a smoother message > processing flow by reducing the number of key presses needed for most > common operations. > --- >

[PATCH] emacs: call "notmuch tag" only once when archiving a thread

Quoth Aaron Ecay on Jan 08 at 7:56 pm: > On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula wrote: > > [...] > > > In the show view it only modifies the messages that are currently > > visible. This is to make sure you don't accidentally archive things that > > have arrived after refreshing the

[PATCH 1/4] emacs: new customization variable to exclude "deleted" messages from search

Jameson, One comment On Sat, 7 Jan 2012 14:28:11 -0800, Jameson Graef Rollins wrote: > The new customization variable, notmuch-search-exclude-deleted, when > set to t, will exclude any messages with the "deleted" tag from > searches. > > Additionally, specifying "tag:deleted" in the search

[PATCH 4/4] emacs: Use the new JSON reply format.

Adam, One comment below. On Sun, 8 Jan 2012 00:52:42 -0700, Adam Wolfe Gordon wrote: > From: Adam Wolfe Gordon > > Using the new JSON reply format allows emacs to quote HTML parts > nicely by first parsing them with w3m, then quoting them. This is > very useful for

[PATCH 0/4] Quoting HTML-only emails in replies redux

On Sun, 8 Jan 2012 00:52:38 -0700, Adam Wolfe Gordon wrote: [...] > > There should probably be some customize variables for this in emacs, to > control > (for example) whether to quote HTML parts and whether to prefer HTML or > plaintext parts for quoting. Any

[PATCH 1/4] emacs: new customization variable to exclude "deleted" messages from search

> > @@ -927,6 +932,9 @@ The optional parameters are used as follows: > > (set 'notmuch-search-target-thread target-thread) > > (set 'notmuch-search-target-line target-line) > > (set 'notmuch-search-continuation continuation) > > +(when (and notmuch-search-exclude-deleted > > +

[PATCH 1/4] emacs: new customization variable to exclude "deleted" messages from search

m query parser, but I think hacking around that by > inspecting the query string is a fine interim solution. (One of these > months I'll dust off the query parser, really!) Very much looking forward to it! 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/20120108/3afe3c7f/attachment-0001.pgp>

[PATCH 1/4] emacs: new customization variable to exclude "deleted" messages from search

Quoth Jameson Graef Rollins on Jan 08 at 6:34 pm: > On Sun, 8 Jan 2012 20:49:38 -0500, Austin Clements > wrote: > > > > @@ -927,6 +932,9 @@ The optional parameters are used as follows: > > > > (set 'notmuch-search-target-thread target-thread) > > > > (set 'notmuch-search-target-line

[PATCH 2/4] emacs: repurpose notmuch-show-archive-thread-internal function for general thread tagging

ame: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/ebb248b7/attachment.pgp>

[PATCH 1/4] emacs: new customization variable to exclude "deleted" messages from search

Quoth myself on Jan 08 at 8:49 pm: > > > @@ -927,6 +932,9 @@ The optional parameters are used as follows: > > > (set 'notmuch-search-target-thread target-thread) > > > (set 'notmuch-search-target-line target-line) > > > (set 'notmuch-search-continuation continuation) > > > +

notmuch git's disk is full! ERROR pushing.

e: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20120108/9cd16c42/attachment.pgp>

  1   2   >