searching for multiple tags

2018-03-16 Thread Brian May
Hello,

How do I search for emails containing multiple tags?

I have tried:

tag:unread tag:important

However, this finds emails that contain either the unread tag or the
important tag. Not emails that contain both.

Am I doing something wrong?

This is version 0.23.7-3 in Debian/stretch.

Thanks
-- 
Brian May 
https://linuxpenguins.xyz/brian/
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: Crash with Python bindings

2018-03-16 Thread Daniel Kahn Gillmor
On Fri 2018-03-16 19:30:37 +0100, Floris Bruynooghe wrote:
> If someone can hook pytest runs with various python versions into the
> notmuch test suit I'd be very much obliged and probably have another go
> at this as it's still an interesting problem and gives a nice way
> forward.

I don't really know what this request means -- so maybe that means that
i'm not the right person for the task, which is fine.

but it's also possible that the right person for the task *also* doesn't
know what you're asking for, so if you could elaborate a bit further
i think that would be super helpful :)

thanks for looking into this further!

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


Re: Crash with Python bindings

2018-03-16 Thread Floris Bruynooghe
Hi all,

David Bremner  writes:

> "W. Trevor King"  writes:
>
>> you can avoid the abort (which happens when q.__del__ is called after
>> db.__del__).  We could make that sort of cleanup easier with context
>> managers for Query objects (we have them for databases since [3]), and
>> they look like the only object that keep an internal database
>> reference:
>>
>>   with Database() as db:
>> with Query(db, "*") as q:
>>   # do something with q
>> db.close()
>>
>
> I'm reminded [1] that this problem still exists. If noone has any idea
> of a fix, should we document one of the workarounds?

This is exactly what I have fixed in my alternative bindings which I
created around the end of last year [0].  So we do have an idea of how
to fix this, at the time I said I do believe that it's possible to also
do this for the existing bindings even though it is a lot of work.
After some talking between dkg and me we got to a way forward which
proposed this, but I must admit that after messing a little with getting
a pytest run integrated into the notmuch test-suite instead of using tox
I lost momentum on the project and didn't advance any further.

If someone can hook pytest runs with various python versions into the
notmuch test suit I'd be very much obliged and probably have another go
at this as it's still an interesting problem and gives a nice way
forward.

Cheers,
Floris

[0] https://github.com/flub/notmuch/tree/cffi/bindings/python-cffi
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: emacs-notmuch: Set variables based on From when composing

2018-03-16 Thread David Bremner
Thomas Schneider  writes:

> Hello list,
>
> I use notmuch with the Emacs frontend and multiple accounts.  I’d like
> it to set the domain part of Message-Id header of any mail I compose to
> something sensible, e.g. the FQDN of the host (which does not seem to be
> easy, see [0]) or the domain part of the From header.

There is some discussion on the wiki of using gnus-alias and
message-templ with notmuch. The latter is more about setting headers.

>
> I was thinking about setting message-user-fqdn based on the From header
> in an appropriate hook, but I haven’t found yet where and how to do
> this.

There is notmuch-mua-send-hook (which by default just runs message-send-hook)

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


Re: Crash with Python bindings

2018-03-16 Thread Justus Winter
David Bremner  writes:

> "W. Trevor King"  writes:
>
>> you can avoid the abort (which happens when q.__del__ is called after
>> db.__del__).  We could make that sort of cleanup easier with context
>> managers for Query objects (we have them for databases since [3]), and
>> they look like the only object that keep an internal database
>> reference:
>>
>>   with Database() as db:
>> with Query(db, "*") as q:
>>   # do something with q
>> db.close()

So while this shouldn't crash of course, this code is wrong.  The
context manager closes the database, so doing db.close() at the end of
the block is superfluous.

> I'm reminded [1] that this problem still exists. If noone has any idea
> of a fix, should we document one of the workarounds?

I don't remember the details, but the different semantics of garbage
collection and talloc was problematic.  In essence, every wrapping
Python object must keep a reference to its parent (as in parent in the
talloc hierarchy).

The bug report [1] sounds like that the crash happens at interpreter
shutdown, where iirc the objects destructors are called in arbitrary
order.


Justus


signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: Crash with Python bindings

2018-03-16 Thread David Bremner
"W. Trevor King"  writes:

> you can avoid the abort (which happens when q.__del__ is called after
> db.__del__).  We could make that sort of cleanup easier with context
> managers for Query objects (we have them for databases since [3]), and
> they look like the only object that keep an internal database
> reference:
>
>   with Database() as db:
> with Query(db, "*") as q:
>   # do something with q
> db.close()
>

I'm reminded [1] that this problem still exists. If noone has any idea
of a fix, should we document one of the workarounds?

  
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893057
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: Address Completion No Longer Working

2018-03-16 Thread David Bremner
david wen riccardi-zhu  writes:

> Hi David,
>
> My apologies if I am missing something obvious, but I'm getting 
> the following:
>
> Cannot find notmuch-emacs source directory
>
> I've tried running the script from both my home directory and my 
> .emacs.d. The script states:
>
> ;; Try the notmuch emacs client located in ../emacs/ directory
>

I guess you need an unpacked copy of the source to run this. Sorry, I
didn't think that through.

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