unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Sandra Snan <sandra.snan@idiomdrottning.org>
To: "Steven Allen" <steven@stebalien.com>,
	"Antoine Beaupré" <anarcat@debian.org>,
	"Notmuch list" <notmuch@notmuchmail.org>
Cc: dkg@fifthhorseman.net, dme@dme.org
Subject: Re: revisiting Autocrypt in notmuch, MVP
Date: Sun, 25 Feb 2024 10:40:35 +0100	[thread overview]
Message-ID: <87frxgc25o.fsf@ellen.idiomdrottning.org> (raw)
In-Reply-To: <87h6hxdw2b.fsf@stebalien.com>

Steven Allen <steven@stebalien.com> writes:

> There's actually a pretty decent autocrypt package[1] for Emacs, 
> only lacking notmuch integration. But writing that based on the 
> mu4e integration should be pretty trivial. 
> 
> [1]: https://git.sr.ht/~pkal/autocrypt/ 

I've been working on that actually so check out that project's 
mailing lists for the patches I've been sending. I've been seeing 
some weird behavior when testing and I wanna iron out all the 
kinks before we merge it, but patches-to-my-patches in that regard 
are more than welcome.♥︎

There are some huge differences between notmuch and mu4e with 
regards to the timing of message access and hooks. Please check 
the commit history of my patches on pkal's mailing list, or get my 
dev repo at

git clone https://idiomdrottning.org/autocrypt

I think my code here is solid and my remaining issues (I've been 
seeing incompabilities with Delta Chat) are with the autocrypt 
library and not with my interface code, but, more eyes would be 
good.

Note that since autocrypt aspires to become an ELPA project you need FSF
assignment forms to work on it.\r

  reply	other threads:[~2024-02-25  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 18:10 revisiting Autocrypt in notmuch, MVP Antoine Beaupré
2024-02-23  3:22 ` Antoine Beaupré
2024-02-23 17:14   ` Antoine Beaupré
2024-02-25  4:09     ` Steven Allen
2024-02-25  9:40       ` Sandra Snan [this message]
2024-02-25 16:33         ` Steven Allen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87frxgc25o.fsf@ellen.idiomdrottning.org \
    --to=sandra.snan@idiomdrottning.org \
    --cc=anarcat@debian.org \
    --cc=dkg@fifthhorseman.net \
    --cc=dme@dme.org \
    --cc=notmuch@notmuchmail.org \
    --cc=steven@stebalien.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).