On Thu, Aug 04 2016, Yuri D'Elia <wav...@thregr.org> wrote:
> The problem is that the search I've built includes both existing
> messages and unread ones (with a buffer of a day). So even though I get
> a new (unread) message, some existing messages in the thread also match.
>
On Thu, Aug 04 2016, Jani Nikula wrote:
>> I'd like to jump directly to the first unread message (and in detail, to
>> the first message that actually matches the query!). It's really not
>> great to have to find what message matched the query, especially for
>> long-running
Hi everyone, I'm experimenting with notmuch-emacs.el (straight from
git), and I have a few questions after a few days of testing.
The search buffer packs messages in threads by default. Is there a way
to have a flat list of strictly matching messages when needed?
For example, for a query like
Hi everyone,
I'm a bit baffled by the query syntax. Reading the manual:
``Each term in the query will be implicitly connected by a logical AND
if no explicit operator is provided (except that terms with a common
prefix will be implicitly combined with OR).''
I would have assumed that:
term1
On Mon, Aug 29 2016, David Bremner <da...@tethera.net> wrote:
> Yuri D'Elia <wav...@thregr.org> writes:
>
>> term1 AND (tag:term2 OR tag:term3)
>>
>> am I right? Is this a feature of the xapian query syntax? (can it be
>> tweaked to _unconditionall
On Mon, Aug 29 2016, Charlie Allom wrote:
> You can debug what the real query is by adding NOTMUCH_DEBUG_QUERY=1 to
> your search:
>
> 12:29 YELP-CHARLIE~[local@2.7.12] % NOTMUCH_DEBUG_QUERY=1 notmuch search
> 'term1 (tag:term2 tag:term3)'
> Query string is:
>