From: Giovanni Biscuolo <g@xelera.eu>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: help-gnu-emacs@gnu.org, Philip Kaludercic <philipk@posteo.net>,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: problems importing keys via epa-search-keys
Date: Sun, 12 Mar 2023 10:32:35 +0100 [thread overview]
Message-ID: <877cvmwc0c.fsf@xelera.eu> (raw)
In-Reply-To: <m2a60jrlau.fsf@fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Hi Filipp
Filipp Gunbin <fgunbin@fastmail.fm> writes:
> Hi Giovanni,
>
> On 11/03/2023 08:05 +0100, Giovanni Biscuolo wrote:
>
> [...]
>
>> I'm using Guix so I'll try to apply your patch for Emacs 28.2 to that
>> package and submit it for inclusion in official Guix distribution.
>
> No need for that, I'll install it either on master or on emacs-29,
> depending on what Eli says.
Fine thanks, but I'd backport that patch to 28.2 in Guix, also.
>> AFAIU there's no bug report for this, or am I wrong? In case there
>> isn't one I'm going to submit a new bug report.
>
> No need for that either. But yes, it's better to submit problems using
> M-x report-emacs-bug, for the future.
I was not sure it was a bug but next time I'm going to use it, thanks!
Happy hacking, Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-03-12 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 7:14 problems importing keys via epa-search-keys Giovanni Biscuolo
2023-03-10 22:58 ` Filipp Gunbin
2023-03-11 7:05 ` Giovanni Biscuolo
2023-03-11 22:10 ` Filipp Gunbin
2023-03-12 9:32 ` Giovanni Biscuolo [this message]
2023-03-11 7:17 ` Eli Zaretskii
2023-03-11 23:04 ` Filipp Gunbin
2023-03-12 6:33 ` Eli Zaretskii
2023-03-13 12:37 ` Filipp Gunbin
2023-03-13 14:43 ` Eli Zaretskii
2023-03-13 17:40 ` Filipp Gunbin
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=877cvmwc0c.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=eliz@gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=help-gnu-emacs@gnu.org \
--cc=philipk@posteo.net \
/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.
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).