[PATCH 1/2] NEWS: notmuch address
--- NEWS | 8 1 file changed, 8 insertions(+) diff --git a/NEWS b/NEWS index 8d7ed0a..16cc002 100644 --- a/NEWS +++ b/NEWS @@ -35,6 +35,14 @@ Stopped `notmuch dump` failing if someone writes to the database limits output of message IDs to messages matching search terms that have at least `N` files associated with them. +Added `notmuch address` subcommand + + This new subcommand searches for messages matching the given search + terms, and prints the addresses from them. Duplicate addresses are + filtered out. The `--output` option controls which of the following + information is printed: sender addresses, recipient addresses and + count of duplicate addresses. + Emacs Interface --- -- 2.1.1 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH 2/2] doc: Minor fixes related to notmuch-address
- Add notmuch-address to HTML index - Remove extra '*' --- doc/index.rst| 1 + doc/man1/notmuch.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/index.rst b/doc/index.rst index ba6d5b4..3f0e6e6 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -8,6 +8,7 @@ Contents: :titlesonly: man1/notmuch + man1/notmuch-address man1/notmuch-compact man1/notmuch-config man1/notmuch-count diff --git a/doc/man1/notmuch.rst b/doc/man1/notmuch.rst index 98590a4..b33738e 100644 --- a/doc/man1/notmuch.rst +++ b/doc/man1/notmuch.rst @@ -129,7 +129,7 @@ SEE ALSO **notmuch-hooks(5)**, **notmuch-insert(1)**, **notmuch-new(1)**, **notmuch-reply(1)**, **notmuch-restore(1)**, **notmuch-search(1)**, **notmuch-search-terms(7)**, **notmuch-show(1)**, **notmuch-tag(1)**, -***notmuch-address(1)** +**notmuch-address(1)** The notmuch website: **http://notmuchmail.org** -- 2.1.1 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail
On Tue, Sep 02 2014, Tomi Ollila wrote: On Tue, Sep 02 2014, Daniel Kahn Gillmor d...@fifthhorseman.net wrote: On 08/30/2014 03:37 AM, Jani Nikula wrote: I'm inclined to think this is a bug in message-mode. I agree it's a bug in message-mode, not in notmuch itself. I think it might be here: http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/head:/lisp/gnus/mml.el#L258 (it takes time to load, please wait...) If cond does not match, then don't fail... This looks to have been fixed in emacs at the end of September 2014. ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Synchronising mail and notmuch tags between machines
I've written some code to synchronise mail between my server and laptop. I have notmuch running on both machine, whenever mail is added to notmuch, it is tagged as needing to be copied to the other machine, the tags are sync-to-laptop and sync-to-server. Whenever I modify the tags on a mail I'm careful to add the sync tag. My mail reader is configured to add the sync tag whenever I make any changes to a mail. Here is the code: https://github.com/EdwardBetts/notmuch-pushy/ The synchronise code opens each database and checks for messages that need to be synchronised, the tags are copied to the other database, if the mail is new then content is copied as well. Then the sync tag is removed from the source message. I'm using a Python RPC module called pushy, it provides a simple way to connect two python interpreters on different machines. Pushy provides proxy objects to access remote objects as if they are local. These means I can access the local and remote notmuch databases from within the same piece of code. All the communication happens over ssh, and pushy even provides methods for copying files between the machines. https://pythonhosted.org/pushy/ https://github.com/pushyrpc/pushy My main todo item is reducing the amount of time that the write lock is held. I should copy messages back and forth before grabbing the write lock to update the tags. It would be helpful if the notmuch would always add the sync tag when a message was modified, unless the sync tag is explicitly being removed. That way there is no risk of me forgetting to add the sync tag when I'm modifying tags using the command line tools. -- Edward. ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH 1/2] NEWS: notmuch address
--- NEWS | 8 1 file changed, 8 insertions(+) diff --git a/NEWS b/NEWS index 8d7ed0a..16cc002 100644 --- a/NEWS +++ b/NEWS @@ -35,6 +35,14 @@ Stopped `notmuch dump` failing if someone writes to the database limits output of message IDs to messages matching search terms that have at least `N` files associated with them. +Added `notmuch address` subcommand + + This new subcommand searches for messages matching the given search + terms, and prints the addresses from them. Duplicate addresses are + filtered out. The `--output` option controls which of the following + information is printed: sender addresses, recipient addresses and + count of duplicate addresses. + Emacs Interface --- -- 2.1.1
[PATCH 2/2] doc: Minor fixes related to notmuch-address
- Add notmuch-address to HTML index - Remove extra '*' --- doc/index.rst| 1 + doc/man1/notmuch.rst | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/index.rst b/doc/index.rst index ba6d5b4..3f0e6e6 100644 --- a/doc/index.rst +++ b/doc/index.rst @@ -8,6 +8,7 @@ Contents: :titlesonly: man1/notmuch + man1/notmuch-address man1/notmuch-compact man1/notmuch-config man1/notmuch-count diff --git a/doc/man1/notmuch.rst b/doc/man1/notmuch.rst index 98590a4..b33738e 100644 --- a/doc/man1/notmuch.rst +++ b/doc/man1/notmuch.rst @@ -129,7 +129,7 @@ SEE ALSO **notmuch-hooks(5)**, **notmuch-insert(1)**, **notmuch-new(1)**, **notmuch-reply(1)**, **notmuch-restore(1)**, **notmuch-search(1)**, **notmuch-search-terms(7)**, **notmuch-show(1)**, **notmuch-tag(1)**, -***notmuch-address(1)** +**notmuch-address(1)** The notmuch website: **http://notmuchmail.org** -- 2.1.1
[Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value sends unencrypted mail
On Tue, Sep 02 2014, Tomi Ollila wrote: > On Tue, Sep 02 2014, Daniel Kahn Gillmor wrote: > >> On 08/30/2014 03:37 AM, Jani Nikula wrote: >>> I'm inclined to think this is a bug in message-mode. >> >> I agree it's a bug in message-mode, not in notmuch itself. > > I think it might be here: > > http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/head:/lisp/gnus/mml.el#L258 > > (it takes time to load, please wait...) > > If cond does not match, then don't fail... This looks to have been fixed in emacs at the end of September 2014.
Synchronising mail and notmuch tags between machines
I've written some code to synchronise mail between my server and laptop. I have notmuch running on both machine, whenever mail is added to notmuch, it is tagged as needing to be copied to the other machine, the tags are sync-to-laptop and sync-to-server. Whenever I modify the tags on a mail I'm careful to add the sync tag. My mail reader is configured to add the sync tag whenever I make any changes to a mail. Here is the code: https://github.com/EdwardBetts/notmuch-pushy/ The synchronise code opens each database and checks for messages that need to be synchronised, the tags are copied to the other database, if the mail is new then content is copied as well. Then the sync tag is removed from the source message. I'm using a Python RPC module called pushy, it provides a simple way to connect two python interpreters on different machines. Pushy provides proxy objects to access remote objects as if they are local. These means I can access the local and remote notmuch databases from within the same piece of code. All the communication happens over ssh, and pushy even provides methods for copying files between the machines. https://pythonhosted.org/pushy/ https://github.com/pushyrpc/pushy My main todo item is reducing the amount of time that the write lock is held. I should copy messages back and forth before grabbing the write lock to update the tags. It would be helpful if the notmuch would always add the sync tag when a message was modified, unless the sync tag is explicitly being removed. That way there is no risk of me forgetting to add the sync tag when I'm modifying tags using the command line tools. -- Edward.
