Re: 'notmuch search thread:<>' lists multiple threads

2018-04-07 Thread David Bremner
"Naveen N. Rao" writes: > Greetings-- > If I search for threads matching a specific thread-id, I am seeing > multiple results: > > $ notmuch search --output=threads thread:000c4d20 > thread:000c4d1e > thread:000c4d20 This looks like a

[PATCH] doc: add a section on quoting to notmuch-search-terms(7)

2018-04-07 Thread David Bremner
I think we've diverged enough from the Xapian query parser that we can't rely on that syntax description [1]. As far as I can tell, [1] also only discusses quotes in the context of phrases. [1]: https://xapian.org/docs/queryparser.html --- doc/man7/notmuch-search-terms.rst | 22

Re: [PATCH 1/2] configure: detect which versions of python can run pytest

2018-04-07 Thread Tomi Ollila
On Sun, Apr 08 2018, Tomi Ollila wrote: > On Sat, Apr 07 2018, David Bremner wrote: > >> Based on a patch from Florian [1]. >> >> [1]: id:py3ibmevqnna@devork.be >> --- >> configure | 20 +++- >> 1 file changed, 19 insertions(+), 1 deletion(-) >> >> diff --git a/configure

Re: [PATCH 1/2] configure: detect which versions of python can run pytest

2018-04-07 Thread Tomi Ollila
On Sat, Apr 07 2018, David Bremner wrote: > Based on a patch from Florian [1]. > > [1]: id:py3ibmevqnna@devork.be > --- > configure | 20 +++- > 1 file changed, 19 insertions(+), 1 deletion(-) > > diff --git a/configure b/configure > index b177b141..c14e6f8b 100755 > ---

remix of pytest runner

2018-04-07 Thread David Bremner
I didn't love the idea of an evergrowing list of variables for versions of python, since to add or delete a version we'd have to update several places, even with the use of functions. This version uses one variable, which because configure is supposed to be fairly portable is a space seperated

[PATCH 1/2] configure: detect which versions of python can run pytest

2018-04-07 Thread David Bremner
Based on a patch from Florian [1]. [1]: id:py3ibmevqnna@devork.be --- configure | 20 +++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/configure b/configure index b177b141..c14e6f8b 100755 --- a/configure +++ b/configure @@ -571,6 +571,24 @@ if [

[PATCH 2/2] test: pytest runner for the test suite

2018-04-07 Thread David Bremner
The 'test_subtest_known_broken' should be removed when there are actual tests to run. Based on a function from Tomi [1] [1]: id:m2r2nq23r9@guru.guru-group.fi --- test/T391-pytest.sh | 14 ++ 1 file changed, 14 insertions(+) create mode 100755 test/T391-pytest.sh diff --git

Re: Database corruption after clean rebuild

2018-04-07 Thread Olly Betts
On Sat, Apr 07, 2018 at 12:17:39PM -0300, David Bremner wrote: > Javier Garcia writes: > > > The following is a solid workaround I've stumbled upon. Afew no longer > > complains and database corruption is gone. > > > > $ notmuch compact > > $ xapian-check

Re: experimenting with pytest tests

2018-04-07 Thread Tomi Ollila
On Sat, Apr 07 2018, Floris Bruynooghe wrote: > Hi, > > From another conversation on this list I've dug up my earlier attempts > at integrating a pytest run into the notmuch testing suite. I'd be > grateful for some guidance on whether this is the right way to go about > things. good stuff,

Re: Database corruption after clean rebuild

2018-04-07 Thread David Bremner
Javier Garcia writes: > Unfortunately I can't share my emails without the approval of other > parties. The minimum subsets that trigger the error are in the range of > 1000-5000 mails, so asking each and everyone of them is out of my reach. > I tried to replicate the

Re: Database corruption after clean rebuild

2018-04-07 Thread Javier Garcia
Unfortunately I can't share my emails without the approval of other parties. The minimum subsets that trigger the error are in the range of 1000-5000 mails, so asking each and everyone of them is out of my reach. I tried to replicate the problem using just spam folders without success. The

experimenting with pytest tests

2018-04-07 Thread Floris Bruynooghe
Hi, From another conversation on this list I've dug up my earlier attempts at integrating a pytest run into the notmuch testing suite. I'd be grateful for some guidance on whether this is the right way to go about things. Here's the diff of configure: diff --git a/configure b/configure index

Re: Database corruption after clean rebuild

2018-04-07 Thread David Bremner
Javier Garcia writes: > I've applied the path to notmuch 0.26.1 without success. > > $ rm -rf ~/.mail/.notmuch > $ LD_LIBRARY_PATH=/hidden-path/notmuch-0.26.1/lib/:$LD_LIBRARY_PATH > ./notmuch new >    Found 20065 total files (that's not much mail). >    Processed 20065

Re: Database corruption after clean rebuild

2018-04-07 Thread Javier Garcia
I've applied the path to notmuch 0.26.1 without success. $ rm -rf ~/.mail/.notmuch $ LD_LIBRARY_PATH=/hidden-path/notmuch-0.26.1/lib/:$LD_LIBRARY_PATH ./notmuch new    Found 20065 total files (that's not much mail).    Processed 20065 total files in 58s (341 files/sec.).    Added 19605 new