[Nicholas D Steeves] Bug#927315: elpa-notmuch: please fix notmuch-tag's limitation of spaces in tag name (+this_tag form is too strict)

2019-04-18 Thread David Bremner
--- Begin Message --- Package: elpa-notmuch Version: 0.28.3-1 Severity: minor From within *notmuch-search-tag:Red label* I expected one of +"Red label", +'Red label', +"Red\ label", and +'Red\ label', plus variations with the '+' inside quotes would work, but it doesn't seem to. notmuch tag

Re: Accidentally unsubscribed?

2019-04-18 Thread David Bremner
Pierre Neidhardt writes: > Hi, > > I've just received an email: > > --8<---cut here---start->8--- > notmuch-boun...@notmuchmail.org (25 mins. ago) (inbox) > Subject: You have been unsubscribed from the notmuch mailing list > --8<---cut

Re: Unexpected output of "notmuch new --quiet"

2019-04-18 Thread Ralph Seichter
* David Bremner: > I could imagine more levels of quiet, but I don't know if it is worth > the trouble. I currently redirect stderr to /dev/null because the actual number of these "ignoring non-mail file" notices is much higher, but that means I don't get to see actual errors which is quite a

Re: Unexpected output of "notmuch new --quiet"

2019-04-18 Thread David Bremner
Ralph Seichter writes: > * David Bremner: > >> I could imagine more levels of quiet, but I don't know if it is worth >> the trouble. > > I currently redirect stderr to /dev/null because the actual number of > these "ignoring non-mail file" notices is much higher, but that means I > don't get to

Re: Unexpected output of "notmuch new --quiet"

2019-04-18 Thread Ralph Seichter
* David Bremner: > I guess if you have a simple way of distinguishing the cases which you > want to consider as errrors, we can revisit the idea. Personally, I'd go with these decreasing levels of severity: Fatal: Execution must stop immediately to prevent damage, error message may or may

Re: Unexpected output of "notmuch new --quiet"

2019-04-18 Thread David Bremner
Ralph Seichter writes: > * David Bremner: > >> I guess if you have a simple way of distinguishing the cases which you >> want to consider as errrors, we can revisit the idea. > > Personally, I'd go with these decreasing levels of severity: [snip] > I don't know if this is a fit for Notmuch, but

Re: [PATCH 1/2] CLI/reindex: fix memory leak

2019-04-18 Thread David Bremner
David Bremner writes: > Since message is owned by messages, it was held for the entire run of > the program. This in turn means that the Xapian::Document objects are > not freed, and thus one ends up with (effectively) a copy of one's > entire mailstore in memory when running Pushed this one to