From: Manuel Giraud via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67704@debbugs.gnu.org, Tassilo Horn <tsdh@gnu.org>
Subject: bug#67704: 30.0.50; Emacs hangs indefinitely when writing GPG-encrypted file
Date: Fri, 08 Dec 2023 09:11:22 +0100 [thread overview]
Message-ID: <87h6ktun9x.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83cyvh1870.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 08 Dec 2023 09:09:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Tassilo Horn <tsdh@gnu.org>
>> Date: Fri, 08 Dec 2023 07:49:13 +0100
>>
>>
>> I have several GPG-encrypted files such as ~/.authinfo.gpg which I use
>> as auth-source. I can still open them fine where I get a pinentry
>> dialog the first time until the password is cached in the gpg-agent.
>> However, I cannot save/write such files from emacs anymore which used to
>> work flawlessly for many years.
>>
>> When I try to save, emacs just seems to hang indefinitely. Setting
>> debug-on-quit and then C-g-ing reveals it hangs in there (emacs -Q):
>
> Isn't this the problem with GnuPG described in PROBLEMS under "Saving
> a file encrypted with GnuPG via EasyPG hangs"?
Hi,
FWIW, I also observe this bug and I have gnupg-2.4.3… So maybe we'll
have to fix this in Emacs.
--
Manuel Giraud
next prev parent reply other threads:[~2023-12-08 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 6:49 bug#67704: 30.0.50; Emacs hangs indefinitely when writing GPG-encrypted file Tassilo Horn
2023-12-08 7:09 ` Eli Zaretskii
[not found] ` <87cyvhb1zh.fsf@gnu.org>
2023-12-08 7:38 ` Eli Zaretskii
2023-12-08 8:11 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-12-08 8:48 ` Eli Zaretskii
2023-12-08 8:59 ` Tassilo Horn
2023-12-08 11:57 ` Eli Zaretskii
2023-12-08 13:16 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-08 13:08 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ktun9x.fsf@ledu-giraud.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=67704@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=tsdh@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.