The new `body:` field (in Xapian terms) or prefix (in slightly
sloppier notmuch) terms allows matching terms that occur only in the
body.
Unprefixed query terms should continue to match anywhere (header or
body) in the message.
This follows a suggestion of Olly Betts to use the facility (since
David Bremner writes:
> I had another thought about user prefixes. I wonder if they should all
> be forcibly prefixed with something that prevents collisions, to prevent
> later pain if we add an "official" prefix with the same name. A quick
> tests suggest it would work to use something like _
In certain conditions the parallel calls to sphinx-build could
collide, yielding a crash like
Exception occurred:
File "/usr/lib/python3/dist-packages/sphinx/environment.py", line 1261, in
get_doctree
doctree = pickle.load(f)
EOFError: Ran out of input
---
I first observed this on
Yang Sheng writes:
> Fix notmuch-describe-key crashing for the following two cases
> 1. format-kbd-macro cannot deal with keys like [(32 . 126)], switch to
> use key-description instead.
> 2. if a function in the current keymap is not bounded, it will crash
> the whole process. We check if it is
David Bremner writes:
> This obsoletes [1]
> This is getting closer to mergable, but it still needs at least to
> sanity check the names of user defined prefixes (see point (a) below).
>
> The main differences from [1] are
>
> (a) xapian prefixes are no longer defined via upper casing, as this
* Gregor Zattler:
> my procmmail scripts recognize mailing list headers and in the end
> there is a list of all mailing lists I ever got mails from [...]
Interesting method. I don't use procmail, but I wrote a small shell
script that scans my existing Maildir storage for List-Post headers and
