all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Filipp Gunbin <fgunbin@fastmail.fm>
To: stardiviner <numbchild@gmail.com>
Cc: 63256@debbugs.gnu.org
Subject: bug#63256: 30.0.50; EasyPG seems has a bug on saving the encrypted file buffer
Date: Fri, 05 May 2023 17:09:32 +0300	[thread overview]
Message-ID: <m2ttwq50pv.fsf@fastmail.fm> (raw)
In-Reply-To: <CAL1eYuJ1wQ8YSc5+MCXdAufG3REBLpyPBavtm53nNJDZ_ZkgUg@mail.gmail.com> (stardiviner's message of "Thu, 4 May 2023 11:25:10 +0800")

Hi,

On 04/05/2023 11:25 +0800, stardiviner wrote:

[...]

> 1. gpg encrypt a plain text file into "file.org.gpg" with the command "gpg
> -e file.org"
> 2. `$ emacs -Q` press keybinding [C-x C-f] to open the encrypted file
> "file.org.gpg"
> 3. modify the file buffer
> 4. Emacs press [C-x C-s] to save the buffer
> 5. Emacs suspends lost response. Buffer mode-line status is still
> "modified".

[...]

Yes, I've just reported it to GnuPG: https://dev.gnupg.org/T6481.  Let's
see what they say.  

There's --command-fd option which allows to separate command input from
data input, then we perhaps can avoid waiting for BEGIN_ENCRYPTION
before sending data.  But I don't know how to use it from Emacs side: we
need something resembling coreutils's mkfifo, which we open for writing
in Emacs (like a process), and pass it's fd to gpg.  I'm not expert in
these things.

Maybe someone else here has ideas.

Filipp





  reply	other threads:[~2023-05-05 14:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  3:25 bug#63256: 30.0.50; EasyPG seems has a bug on saving the encrypted file buffer stardiviner
2023-05-05 14:09 ` Filipp Gunbin [this message]
2024-01-23 18:13 ` Filipp Gunbin
2024-01-25 23:44   ` Stefan Kangas
2024-01-26 16:29     ` Filipp Gunbin
2024-01-28  1:24       ` Stefan Kangas
2024-01-28  1:25         ` Stefan Kangas
2024-01-28  6:23         ` Eli Zaretskii

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=m2ttwq50pv.fsf@fastmail.fm \
    --to=fgunbin@fastmail.fm \
    --cc=63256@debbugs.gnu.org \
    --cc=numbchild@gmail.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 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.