From: philipk@posteo.net (Philip K.)
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39886@debbugs.gnu.org, stefan@marxist.se
Subject: bug#39886: [PATCH] Add EPA keyserver client
Date: Sun, 09 Aug 2020 13:28:11 +0200 [thread overview]
Message-ID: <87h7tc5a9g.fsf@posteo.net> (raw)
In-Reply-To: <87h7tcw3hq.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 09 Aug 2020 11:52:17 +0200)
Lars Ingebrigtsen <larsi@gnus.org> writes:
> "Philip K." <philipk@posteo.net> writes:
>
>> I agree, submitting this as a core-patch was the wrong approach. What's
>> the procedure for submitting a ELPA package?
>
> I was saying that submitting it to Emacs core was the right approach.
> :-)
Oh my, I misread your message. Sorry for that.
> For instance, when a user clicks on a "verify this signed article"
> button in Gnus/rmail, the key should be downloaded from a key server
> automatically, and if I understand your package correctly, it allows
> doing so?
Yes, it implements the protocol and a basic UI. My only issues is that I
wrote this before I dove in to the EPA source, and realized that it more
or les depends on GnuPG. And if GnuGP is alreay given, I could just as
well use it's build-in functionallity for querying the server, without
having to reimplement it in Elisp.
> But for this to work seamlessly, your package has to be in Emacs core,
> otherwise Gnus/rmail can't rely on it as easily.
Couldn't it extend Gnus/rmail externally? Or could Gnus/rmail check if
it's feature is available?
next prev parent reply other threads:[~2020-08-09 11:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 16:23 bug#39886: [PATCH] Add EPA keyserver client Philip K
[not found] ` <CADwFkm=iPrhJaBhntAFcQPnRerHSsTY1Lc1gihMR06fVrVR_cQ@mail.gmail.com>
2020-05-19 10:08 ` Philip K.
2020-05-19 13:50 ` Stefan Kangas
2020-08-08 13:59 ` Lars Ingebrigtsen
2020-08-08 14:42 ` Stefan Kangas
2020-08-08 14:51 ` Colin Baxter
2020-08-08 17:20 ` Philip K.
2020-08-09 9:52 ` Lars Ingebrigtsen
2020-08-09 11:28 ` Philip K. [this message]
2020-08-09 19:41 ` Lars Ingebrigtsen
2021-05-12 16:45 ` Lars Ingebrigtsen
2021-05-12 16:52 ` Philip Kaludercic
2021-05-12 16:57 ` Lars Ingebrigtsen
2021-05-12 17:10 ` Eli Zaretskii
2021-05-12 17:23 ` Philip Kaludercic
2021-05-12 17:24 ` Lars Ingebrigtsen
2021-05-12 17:34 ` Philip Kaludercic
2021-05-12 17:52 ` Philip Kaludercic
2021-05-12 18:00 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7tc5a9g.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=39886@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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://git.savannah.gnu.org/cgit/emacs.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).