On Thu 2017-11-16 08:40:41 -0400, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>
>> The new "auto" decryption policy is not only good for "notmuch show"
>> and "notmuch reindex". It's also useful for indexing messages --
>> there's no good reason to not try to go ahead and index the clearte
On Thu 2017-10-26 18:27:51 -0400, Daniel Kahn Gillmor wrote:
> "notmuch help" doesn't mention "notmuch-emacs-mua" even though we
> support it through the try_external_command() mechanism.
>
> In addition, "notmuch help emacs-mua" doesn't work, even though we
> ship the appropriate manpage.
>
> This
On Thu 2017-10-26 18:28:12 -0400, Daniel Kahn Gillmor wrote:
> ---
> completion/notmuch-completion.bash | 2 +-
> notmuch.c | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
Ping on this patch as well. I think this should be safe and simple to
merge.
--d
When i'm trying to understand a message signature, i care that i know
who it came from (the "validity" of the identity associated with the
key), *not* whether i'm willing to accept the keyholder's other
identity assertions (the "trust" associated with the certificate).
We've been reporting User ID
Daniel Kahn Gillmor writes:
> On Tue 2017-11-28 23:46:11 +0100, Ruben Pollan wrote:
>> Message.get_property (prop) returns a string with the value of the property
>> and
>> Message.get_properties (prop, exact=False) returns a list [(key, value)]
>
> This looks like a sensible approach to me. I'
Patrick Totzke writes:
> Quoting David Bremner (2017-11-28 23:59:26)
>> Floris Bruynooghe writes:
>>
>> >
>> > Lastly there are some downsides to the choices I made:
>> > - I ended up going squarely for CPython 3.6+. Choosing Python
>> > 3 allowed better API design, e.g. with keyword-only pa
David Bremner writes:
> Floris Bruynooghe writes:
>
>>
>> Lastly there are some downsides to the choices I made:
>> - I ended up going squarely for CPython 3.6+. Choosing Python
>> 3 allowed better API design, e.g. with keyword-only parameters
>> etc. Choosing CPython 3.4+ restricts the ma
Quoting David Bremner (2017-11-28 23:59:26)
> Floris Bruynooghe writes:
>
> >
> > Lastly there are some downsides to the choices I made:
> > - I ended up going squarely for CPython 3.6+. Choosing Python
> > 3 allowed better API design, e.g. with keyword-only parameters
> > etc. Choosing CPy
Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) returns a list [(key, value)]
---
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 81 +-
2 files changed,
Quoting Daniel Kahn Gillmor (2017-11-29 02:57:24)
> On Tue 2017-11-28 23:46:11 +0100, Ruben Pollan wrote:
> > Message.get_property (prop) returns a string with the value of the property
> > and
> > Message.get_properties (prop, exact=False) returns a list [(key, value)]
>
> This looks like a sens
10 matches
Mail list logo