[PATCH] NEWS: Consolidate nmbug-status and notmuch-report sections

[W. Trevor King]

These are the same tool; the nmbug-status text just landed before the
name change.  We can also drop the message-url details from NEWS,
since they're already in the man page.
---
The integration fixes requested in [1].

Cheers,
Trevor

[1]: id:87r3f0jgg1.fsf@zancas.localnet
 http://thread.gmane.org/gmane.mail.notmuch.general/21554/focus=22064

 NEWS | 23 ---
 1 file changed, 4 insertions(+), 19 deletions(-)

diff --git a/NEWS b/NEWS
index 768f989..78d4708 100644
--- a/NEWS
+++ b/NEWS
@@ -39,28 +39,13 @@ users looking for generic notmuch reporting tools.
 The default configuration file name (extracted from the `config`
 branch of `NBMGIT` has changed from `status-config.json` to
 `notmuch-report.json` so it is more obviously associated with the
-report-generating script.
+report-generating script.  The configuration file also has a new
+`meta.message-url` setting, which is documented in
+`notmuch-report.json(5)`.
 
-nmbug-status
-
-
-`nmbug-status` now wraps query phrases in parentheses when and-ing
+`notmuch-report` now wraps query phrases in parentheses when and-ing
 them together, to avoid confusion about clause grouping.
 
-`nmbug-status` now supports `meta.message-url` to override the Gmane
-template.  For example, you can use:
-
-{
-  "meta": {
-"message-url": 
"https://groups.google.com/a/opencontainers.org/forum/#!search/messageid$3A%22{message-id}%22;
- ...
-  },
-  ...
-}
-
-To link to messages in the [opencontainers.org Google
-Groups](https://groups.google.com/a/opencontainers.org/forum/#!overview).
-
 Notmuch 0.21 (2015-10-29)
 =
 
-- 
2.1.0.60.g85f0837

___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: FastMail uses xapian for real time search, can we do the same?

[David Bremner]

Edward Betts  writes:

>
> Is there any enthusiasm for adding real time search to notmuch?

It sounds interesting. I do wonder if just better (read, any) retry
handling might give most of the user benefits with fewer moving parts.

I think the real reason that the locking failures bother me less is just
a workflow one: I don't have notmuch-insert / notmuch-new running in the
background, but rather fetch a few few times a day. I'm not saying
everyone should read mail like I do, just explaining why it's less of a
priority for me personally than some other issues.

d

___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH v3 2/2] emacs: `notmuch-show-forward-message' can use `notmuch-mua-new-forward-messages'

[David Bremner]

David Edmondson  writes:

> Which allows `notmuch-mua-new-forward-message' to be removed.

Pushed this series

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH v2] emacs: Allow part preferences to depend on message content.

[David Bremner]

David Edmondson  writes:

> Currently the preference for which sub-part of a multipart/alternative
> part is shown is global. Allow to the user to override the settings on a
> per-message basis by providing the ability to call a function that has
> access to the message to return the discouraged type list.

This patch looks fine, but it needs a smarter monkey than me to rebase
it.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH v1 1/3] emacs: Improve crypto button labels.

[David Bremner]

David Edmondson  writes:

> Make the labels for both encryption and signature buttons share a common
> format, in which both report the status if it is not one of those known.
> ---

Pushed this one patch, since surprisingly it doesn't break the test
suite.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH v1 2/3] emacs: Always insert crypto buttons.

[David Bremner]

David Edmondson  writes:

> When no decryption or signature examination is
> happening (i.e. `notmuch-crypto-process-mime' is `nil') insert buttons
> that indicate this, rather than remaining silent.

I'm afraid starting at patch 2 this series needs rebasing against
master.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH v2 4/4] status-config.json: Remove parens from query entry

[David Bremner]

"W. Trevor King"  writes:

> These are now added by nmbug-status.
> ---
>  devel/nmbug/status-config.json | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/devel/nmbug/status-config.json b/devel/nmbug/status-config.json
> index b926946..48b6f19 100644
> --- a/devel/nmbug/status-config.json
> +++ b/devel/nmbug/status-config.json
> @@ -62,7 +62,7 @@
>   "not tag:notmuch::obsolete",
>   "not tag:notmuch::stale",
>   "not tag:notmuch::wontfix",
> - "(tag:notmuch::moreinfo or tag:notmuch::needs-review)"
> + "tag:notmuch::moreinfo or tag:notmuch::needs-review"
>   ],
>   "title": "Review"
>   }
> -- 
> 2.1.0.60.g85f0837

These are now merged as well.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

Re: [PATCH 5/5] NEWS: Document the notmuch-report branch

[David Bremner]

"W. Trevor King"  writes:

> ---
>  NEWS | 26 ++
>  1 file changed, 26 insertions(+)

I finally merged these. You'll probably want to look at how the NEWS
items for the two notmuch-report series combine. They're also a bit long
for my taste, but I don't think it's worth spending a lot of time fine
tuning NEWS entries.

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch

FastMail uses xapian for real time search, can we do the same?

[Edward Betts]

I've tried using 'notmuch insert' with mutt-kz, the mutt fork that talks to
the notmuch database. Both keep trying to grab the write lock at the same time.

I tag a mail in mutt-kz and it writes the new tag to the database, at the same
time a new mail is coming in. Either 'notmuch insert' has the lock and
my mail client pauses while it retries or notmuch-insert isn't able to get the
write lock and just saves the mail to the maildir and it doesn't get added
until I later run 'notmuch new'.

I guess many people here are using the Emacs client and the problem is partly
avoided because there is a separate thread in the background trying to grab
the write lock and save tag changes. Is that correct?

I wonder if the solution is real time search? xapian can search in multiple
databases. New mails and tag changes can be written to a new database, there
could be one database for inserting new mails and another for changes to the
tags on existing mails. Then there are no problems with write locks. These
databases will be much smaller, so the writes should be faster. There can be a
process that runs once a day to merge the databases.

FastMail have implemented real time search for email with xapian.

Blog post: https://blog.fastmail.com/2014/12/01/email-search-system/

Implementation: https://github.com/brong/cyrus-imapd/tree/fastmail

Is there any enthusiasm for adding real time search to notmuch?
-- 
Edward.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch