excessive thread fusing
Gregor Zattler mentioned some problems with threading at id:20120126004024.GA13704 at shi.workgroup After some off list discussions, I believe I have a smaller test case. The attached maildir contains 24 messages from the org mode list. According to notmuch, these form one thread, but I can't figure out exactly why. It seems like the chronologically first two messages should be a seperate thread. There are several of the infamous malformed ME-E In-reply-to headers, but each of these messages also has a References header; this seems to indicate a case missed by commit cf8aaafbad68. -- next part -- A non-text attachment was scrubbed... Name: test-maildir.tar.gz Type: application/octet-stream Size: 23367 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20140419/a05d081c/attachment-0001.obj>
excessive thread fusing
On Sat, 19 Apr 2014 21:33:36 +0900, David Bremner wrote: > > Gregor Zattler mentioned some problems with threading at > >id:20120126004024.GA13704 at shi.workgroup > > After some off list discussions, I believe I have a smaller test case. > > The attached maildir contains 24 messages from the org mode list. > > According to notmuch, these form one thread, but I can't figure out > exactly why. It seems like the chronologically first two messages should > be a seperate thread. There are several of the infamous malformed ME-E > In-reply-to headers, but each of these messages also has a References > header; this seems to indicate a case missed by commit cf8aaafbad68. > This may not actually be any help, but both hypermail and mhonarc agree that two messages form a separate thread from the rest. I believe that the latter, at least, is the JWZ algorithm. Eric -- ms fnd in a lbry
[PATCH] doc: make notmuch-new summary line more generic
Since 'notmuch new' now takes multiple options, it's confusing to show only one of them in the summary. --- doc/man1/notmuch-new.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst index d11fcee..787ed78 100644 --- a/doc/man1/notmuch-new.rst +++ b/doc/man1/notmuch-new.rst @@ -5,7 +5,7 @@ notmuch-new SYNOPSIS -**notmuch** **new** [--no-hooks] +**notmuch** **new** [options] DESCRIPTION === -- 1.9.1
[PATCH] emacs: Honor debug-on-error for part renderers
Austin Clements writes: > Previously, even if debug-on-error was non-nil, the debugger would not > trap on part renderer errors. This made debugging part renderer bugs > frustrating, so let the debugger trap these errors. pushed d
[PATCH] News for changes from Austin Clements
Austin Clements writes: > --- > NEWS | 12 > 1 file changed, 12 insertions(+) > pushed. d
[PATCH] NEWS for displaying tag changes
On Sat, Apr 19 2014, Mark Walters wrote:
> ---
> I don't know if any special markdown is needed for the two lisp
> expressions: '((".*" nil)) and '((".*" tag)) so that may need tweaking.
>
> Best wishes
>
> Mark
>
> NEWS | 21 +
> 1 file changed, 21 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index 19c6556..ec10c58 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps
>`notmuch-tag-formats` will continue to work as before unless tags
>contain regexp special characters like `.` or `*`.
>
> +Changed tags are now shown in the buffer
> +
> + Previously tag changes made in a buffer were shown immediately. In
> + some cases (particularly automatic tag changes like marking read)
> + this made it hard to see what had happened (e.g., whether the
> + message had been unread).
> +
> + The changes are now shown explicitly in the buffer: by default
> + deleted tags are displayed with red strike-through and added tags
> + are displayed underlined in green (inverse video is used for deleted
> + tags if the terminal does not support strike-through).
> +
> + The variables `notmuch-tag-deleted-formats` and
> + `notmuch-tag-added-formats`, which have the same syntax as
> + `notmuch-tag-formats`, allow this to be customized.
> +
> + Setting `notmuch-tag-deleted-formats` to '((".*" nil))) and
> + `notmuch-tag-added-formats` to '((".*" tag)) will give the old
perhaps just `'((".*" nil))` and `'((".*" tag))`, former with 2 closing
parens ;)
Tomi
> + behavior of hiding deleted tags and showing added tags identically
> + to tags already present.
> +
> Version variable
>
>The new, build-time generated variable `notmuch-emacs-version` is used
> --
> 1.7.10.4
>
> ___
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH v2] NEWS for displaying tag changes
---
Fixed the markdown and the bracket error.
Best wishes
Mark
NEWS | 21 +
1 file changed, 21 insertions(+)
diff --git a/NEWS b/NEWS
index 19c6556..39fa447 100644
--- a/NEWS
+++ b/NEWS
@@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps
`notmuch-tag-formats` will continue to work as before unless tags
contain regexp special characters like `.` or `*`.
+Changed tags are now shown in the buffer
+
+ Previously tag changes made in a buffer were shown immediately. In
+ some cases (particularly automatic tag changes like marking read)
+ this made it hard to see what had happened (e.g., whether the
+ message had been unread).
+
+ The changes are now shown explicitly in the buffer: by default
+ deleted tags are displayed with red strike-through and added tags
+ are displayed underlined in green (inverse video is used for deleted
+ tags if the terminal does not support strike-through).
+
+ The variables `notmuch-tag-deleted-formats` and
+ `notmuch-tag-added-formats`, which have the same syntax as
+ `notmuch-tag-formats`, allow this to be customized.
+
+ Setting `notmuch-tag-deleted-formats` to `'((".*" nil))` and
+ `notmuch-tag-added-formats` to `'((".*" tag))` will give the old
+ behavior of hiding deleted tags and showing added tags identically
+ to tags already present.
+
Version variable
The new, build-time generated variable `notmuch-emacs-version` is used
--
1.7.10.4
[PATCH] NEWS for displaying tag changes
---
I don't know if any special markdown is needed for the two lisp
expressions: '((".*" nil)) and '((".*" tag)) so that may need tweaking.
Best wishes
Mark
NEWS | 21 +
1 file changed, 21 insertions(+)
diff --git a/NEWS b/NEWS
index 19c6556..ec10c58 100644
--- a/NEWS
+++ b/NEWS
@@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps
`notmuch-tag-formats` will continue to work as before unless tags
contain regexp special characters like `.` or `*`.
+Changed tags are now shown in the buffer
+
+ Previously tag changes made in a buffer were shown immediately. In
+ some cases (particularly automatic tag changes like marking read)
+ this made it hard to see what had happened (e.g., whether the
+ message had been unread).
+
+ The changes are now shown explicitly in the buffer: by default
+ deleted tags are displayed with red strike-through and added tags
+ are displayed underlined in green (inverse video is used for deleted
+ tags if the terminal does not support strike-through).
+
+ The variables `notmuch-tag-deleted-formats` and
+ `notmuch-tag-added-formats`, which have the same syntax as
+ `notmuch-tag-formats`, allow this to be customized.
+
+ Setting `notmuch-tag-deleted-formats` to '((".*" nil))) and
+ `notmuch-tag-added-formats` to '((".*" tag)) will give the old
+ behavior of hiding deleted tags and showing added tags identically
+ to tags already present.
+
Version variable
The new, build-time generated variable `notmuch-emacs-version` is used
--
1.7.10.4
[PATCH v2] NEWS: notmuch-init-file and notmuch-emacs-version related news
Tomi Ollila writes: > Along with those, removed trailing space from subsection title. pushed. d
[PATCH] doc: Fix parallel build of roff files
Austin Clements writes: > The roff build rule builds all of the roff files in a single command. > Previously, this was expressed as a multi-target rule, but since this > is equivalent to specifying a copy of the rule for each target, make > -jN could start up to N parallel instances of this command. Fix this > by bottlenecking this rule through a single stamp file. pushed, with comment typofixed. d
[PATCH 1/2] build: add canonicalize_file_name to symbols exported from libnotmuch.so
David Bremner writes: > This is needed for our compat version of canonicalize_file_name to be used. pushed. OpenBSD users: please try commit g2d024ff, to see if it fixes the issues with finding canonicalize_file_name d
[PATCH] News for changes from Austin Clements
--- NEWS | 12 1 file changed, 12 insertions(+) diff --git a/NEWS b/NEWS index 4ceff94..19c6556 100644 --- a/NEWS +++ b/NEWS @@ -46,6 +46,12 @@ Changed format for saved searches saved-search :name) and (cdr saved-search) by (notmuch-saved-search-get saved-search :query) should be sufficient. +The keys of `notmuch-tag-formats` are now regexps + + Previously, the keys were literal strings. Customized settings of + `notmuch-tag-formats` will continue to work as before unless tags + contain regexp special characters like `.` or `*`. + Version variable The new, build-time generated variable `notmuch-emacs-version` is used @@ -60,6 +66,12 @@ Bug fix for saved searches with newlines in them Split lines confuse `notmuch count --batch`, so we remove embedded newlines before calling notmuch count. +Bug fixes for sender identities + + Previously, Emacs would rewrite some sender identities in unexpected + and undesirable ways. Now it will use identities exactly as + configured in `notmuch-identities`. + nmbug - -- 1.9.1
[PATCH] NEWS for displaying tag changes
--- I don't know if any special markdown is needed for the two lisp expressions: '((.* nil)) and '((.* tag)) so that may need tweaking. Best wishes Mark NEWS | 21 + 1 file changed, 21 insertions(+) diff --git a/NEWS b/NEWS index 19c6556..ec10c58 100644 --- a/NEWS +++ b/NEWS @@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps `notmuch-tag-formats` will continue to work as before unless tags contain regexp special characters like `.` or `*`. +Changed tags are now shown in the buffer + + Previously tag changes made in a buffer were shown immediately. In + some cases (particularly automatic tag changes like marking read) + this made it hard to see what had happened (e.g., whether the + message had been unread). + + The changes are now shown explicitly in the buffer: by default + deleted tags are displayed with red strike-through and added tags + are displayed underlined in green (inverse video is used for deleted + tags if the terminal does not support strike-through). + + The variables `notmuch-tag-deleted-formats` and + `notmuch-tag-added-formats`, which have the same syntax as + `notmuch-tag-formats`, allow this to be customized. + + Setting `notmuch-tag-deleted-formats` to '((.* nil))) and + `notmuch-tag-added-formats` to '((.* tag)) will give the old + behavior of hiding deleted tags and showing added tags identically + to tags already present. + Version variable The new, build-time generated variable `notmuch-emacs-version` is used -- 1.7.10.4 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: notmuch, OpenBSD issues
David Mazieres dm-list-email-notm...@scs.stanford.edu writes: I'm using notmuch 0.17 on openbsd (from the ports tree). My problem is that notmuch new is just unbearably slow. I don't know if it's because I'm running the 32-bit (i386) mode or what, but it takes over one second per mail message. E.g., this is typical of what I see when checking for new mail: Processed 18 total files in 20s (0 files/sec.). Added 5 new messages to the database. Linux is 10 times faster. Have you seen any similar performance issues? I didn't realize there was a port. I don't see it in my tree (amd64, recent 5.5-current). I've been building from the git repo. Anyway, yes I have seen similar on an older Mac OS X install I have at home on a G4 PowerBook. I haven't had unbearably slow performance on my amd64 OpenBSD installation, but there is sometimes a noticable lag. I wonder if it would help to enable softupdates on the partition where your database lives? http://www.openbsd.org/faq/faq14.html#SoftUpdates Allan ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] NEWS for displaying tag changes
On Sat, Apr 19 2014, Mark Walters markwalters1...@gmail.com wrote: --- I don't know if any special markdown is needed for the two lisp expressions: '((.* nil)) and '((.* tag)) so that may need tweaking. Best wishes Mark NEWS | 21 + 1 file changed, 21 insertions(+) diff --git a/NEWS b/NEWS index 19c6556..ec10c58 100644 --- a/NEWS +++ b/NEWS @@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps `notmuch-tag-formats` will continue to work as before unless tags contain regexp special characters like `.` or `*`. +Changed tags are now shown in the buffer + + Previously tag changes made in a buffer were shown immediately. In + some cases (particularly automatic tag changes like marking read) + this made it hard to see what had happened (e.g., whether the + message had been unread). + + The changes are now shown explicitly in the buffer: by default + deleted tags are displayed with red strike-through and added tags + are displayed underlined in green (inverse video is used for deleted + tags if the terminal does not support strike-through). + + The variables `notmuch-tag-deleted-formats` and + `notmuch-tag-added-formats`, which have the same syntax as + `notmuch-tag-formats`, allow this to be customized. + + Setting `notmuch-tag-deleted-formats` to '((.* nil))) and + `notmuch-tag-added-formats` to '((.* tag)) will give the old perhaps just `'((.* nil))` and `'((.* tag))`, former with 2 closing parens ;) Tomi + behavior of hiding deleted tags and showing added tags identically + to tags already present. + Version variable The new, build-time generated variable `notmuch-emacs-version` is used -- 1.7.10.4 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH v2] NEWS for displaying tag changes
--- Fixed the markdown and the bracket error. Best wishes Mark NEWS | 21 + 1 file changed, 21 insertions(+) diff --git a/NEWS b/NEWS index 19c6556..39fa447 100644 --- a/NEWS +++ b/NEWS @@ -52,6 +52,27 @@ The keys of `notmuch-tag-formats` are now regexps `notmuch-tag-formats` will continue to work as before unless tags contain regexp special characters like `.` or `*`. +Changed tags are now shown in the buffer + + Previously tag changes made in a buffer were shown immediately. In + some cases (particularly automatic tag changes like marking read) + this made it hard to see what had happened (e.g., whether the + message had been unread). + + The changes are now shown explicitly in the buffer: by default + deleted tags are displayed with red strike-through and added tags + are displayed underlined in green (inverse video is used for deleted + tags if the terminal does not support strike-through). + + The variables `notmuch-tag-deleted-formats` and + `notmuch-tag-added-formats`, which have the same syntax as + `notmuch-tag-formats`, allow this to be customized. + + Setting `notmuch-tag-deleted-formats` to `'((.* nil))` and + `notmuch-tag-added-formats` to `'((.* tag))` will give the old + behavior of hiding deleted tags and showing added tags identically + to tags already present. + Version variable The new, build-time generated variable `notmuch-emacs-version` is used -- 1.7.10.4 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
[PATCH] doc: make notmuch-new summary line more generic
Since 'notmuch new' now takes multiple options, it's confusing to show only one of them in the summary. --- doc/man1/notmuch-new.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst index d11fcee..787ed78 100644 --- a/doc/man1/notmuch-new.rst +++ b/doc/man1/notmuch-new.rst @@ -5,7 +5,7 @@ notmuch-new SYNOPSIS -**notmuch** **new** [--no-hooks] +**notmuch** **new** [options] DESCRIPTION === -- 1.9.1 ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
excessive thread fusing
Gregor Zattler mentioned some problems with threading at id:20120126004024.GA13704@shi.workgroup After some off list discussions, I believe I have a smaller test case. The attached maildir contains 24 messages from the org mode list. According to notmuch, these form one thread, but I can't figure out exactly why. It seems like the chronologically first two messages should be a seperate thread. There are several of the infamous malformed ME-E In-reply-to headers, but each of these messages also has a References header; this seems to indicate a case missed by commit cf8aaafbad68. test-maildir.tar.gz Description: Binary data ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: excessive thread fusing
On Sat, 19 Apr 2014 21:33:36 +0900, David Bremner da...@tethera.net wrote: Gregor Zattler mentioned some problems with threading at id:20120126004024.GA13704@shi.workgroup After some off list discussions, I believe I have a smaller test case. The attached maildir contains 24 messages from the org mode list. According to notmuch, these form one thread, but I can't figure out exactly why. It seems like the chronologically first two messages should be a seperate thread. There are several of the infamous malformed ME-E In-reply-to headers, but each of these messages also has a References header; this seems to indicate a case missed by commit cf8aaafbad68. This may not actually be any help, but both hypermail and mhonarc agree that two messages form a separate thread from the rest. I believe that the latter, at least, is the JWZ algorithm. Eric -- ms fnd in a lbry ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: excessive thread fusing
On Sb, 19 apr 14, 18:52:02, Eric wrote: This may not actually be any help, but both hypermail and mhonarc agree that two messages form a separate thread from the rest. I believe that the latter, at least, is the JWZ algorithm. mutt concurs. Kind regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
