On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> GPGME has a strange failure mode when it is in offline mode, and/or
> when certificates don't have any CRLs: in particular, it refuses to
> accept the validity of any certificate other than a "root" cert.
>
> This can be worked around by setting th
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> This is taken from the same Internet Draft that test/smime/ca.crt
> comes from. See that draft for more details.
> https://www.ietf.org/id/draft-dkg-lamps-samples-02.html#name-pkcs12-object-for-bob
>
> We don't use it yet, but it will be used to d
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> Without this fix, we couldn't run both add_gnupg_home and
> add_gpgsm_home in the same test script.
>
> Signed-off-by: Daniel Kahn Gillmor
> ---
> test/test-lib.sh | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/t
On Wed, Apr 29, 2020 at 8:08 PM David Bremner wrote:
> > I've also read the FAQ:
> > * https://notmuchmail.org/faq/#index8h2
>
> Oops, that needs to be updated.
>
> It is implemented. See notmuch-config(1), under "index.header"
That's perfect. However the `search-terms` man pages doesn't say ho
Ciprian Dorin Craciun writes:
> I've searched the mailing list archives about the `List-Id` feature:
> * https://www.mail-archive.com/notmuch@notmuchmail.org/msg43214.html
> * https://www.mail-archive.com/notmuch@notmuchmail.org/msg22092.html
> * https://www.mail-archive.com/notmuch@notmuchmail.o
I've searched the mailing list archives about the `List-Id` feature:
* https://www.mail-archive.com/notmuch@notmuchmail.org/msg43214.html
* https://www.mail-archive.com/notmuch@notmuchmail.org/msg22092.html
* https://www.mail-archive.com/notmuch@notmuchmail.org/msg14146.html
I've also read the FAQ
Jameson Graef Rollins writes:
> On Wed, Apr 29 2020, David Bremner wrote:
>> I guess I'm a bit leery of removing UI features that presumably at least
>> some people rely on. It's pretty upsetting to have sofware break one's
>> muscle memory.
>
> I dare say there are few people that have muscle m
According to the `devel/schemata` the message object doesn't contain
the thread identifier to which it was assigned in the database.
Sometimes, for example in an UI that displays a search result at
message level, it would be useful to know the thread each message
belongs to, so the user can easily
On Wed, Apr 29 2020, Ciprian Dorin Craciun wrote:
> I think there are two complete different use-cases for the `notmuch` binary:
> * a simple CLI to query the database, in which case the current flags seem OK;
> * a "poor-mans" API to query the database, more bellow;
>
> (I know there already exis
On Wed, Apr 29, 2020 at 6:39 PM David Bremner wrote:
> I guess I'm a bit leery of removing UI features that presumably at least
> some people rely on. It's pretty upsetting to have sofware break one's
> muscle memory.
I think there are two complete different use-cases for the `notmuch` binary:
*
On Wed, Apr 29 2020, David Bremner wrote:
> I guess I'm a bit leery of removing UI features that presumably at least
> some people rely on. It's pretty upsetting to have sofware break one's
> muscle memory.
I dare say there are few people that have muscle memory for the notmuch
command line (espe
Tomi Ollila writes:
> On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
>
>>
>> One final way we could normalize everything and make it less
>> idiosyncratic, with shorter, simpler man pages: deprecate and then drop
>> the --booloption/--no-booloption mechanisms, requiring --booloption=true
>> or -
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> One final way we could normalize everything and make it less
> idiosyncratic, with shorter, simpler man pages: deprecate and then drop
> the --booloption/--no-booloption mechanisms, requiring --booloption=true
> or --booloption=false instead. Once
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
>
> One final way we could normalize everything and make it less
> idiosyncratic, with shorter, simpler man pages: deprecate and then drop
> the --booloption/--no-booloption mechanisms, requiring --booloption=true
> or --booloption=false instead. On
David Bremner wrote:
> Franz Fellner writes:
> > mail takes at least 10 seconds, sometimes even more. It can go into
> > minutes when I get lots of mail (~30...). When I run it after a
> > reboot I can have breakfast while notmuch starts up... This is all on
> > spinning rust. I thought of get
15 matches
Mail list logo