From: Daiki Ueno <ueno@unixuser.org>
To: Romain Francoise <romain@orebokech.com>
Cc: 6723@debbugs.gnu.org, Stefano Zacchiroli <zack@upsilon.cc>
Subject: bug#6723: 24.0.50; gnupg support is no longer able to create .gpg files from scratch
Date: Sun, 25 Jul 2010 20:39:02 +0900 [thread overview]
Message-ID: <87wrsjhju1.fsf@broken.deisui.org> (raw)
In-Reply-To: <87eieraluh.fsf@elegiac.orebokech.com> (Romain Francoise's message of "Sun, 25 Jul 2010 12:37:26 +0200")
Romain Francoise <romain@orebokech.com> writes:
> Stefano Zacchiroli <zack@upsilon.cc> writes:
>
>> Starting from recent Emacs snapshots, I'm no longer able to create
>> encrypted .gpg files on the fly, using Emacs GPG support. I used to do
>> `C-x C-f something.txt.gpg' where something.txt.gpg is a non-existent
>> file, followed by `C-j' to confirm the creation of the file. That now
>> fails with the message reported in recent messages below, i.e.:
>
>> epa-file--find-file-not-found-function: Opening input file: Can't decrypt, ((exit))
> This is probably caused by the following change:
>
> 2010-07-08 Daiki Ueno <ueno@unixuser.org>
>
> * epa-file.el (epa-file-error, epa-file--find-file-not-found-function)
> (epa-file-insert-file-contents): Hack to prevent
> find-file from opening empty buffer when decryptin failed
> (bug#6568).
Good catch. It should be fixed now (as r100895). Thanks.
BTW, does debbugs have a feature to tag epg related bug? I usually
search the bugdb with "encrypt", "decrypt", "gnupg", etc. and possibly
there might have been bugs left unnoticed.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2010-07-25 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 10:06 bug#6723: 24.0.50; gnupg support is no longer able to create .gpg files from scratch Stefano Zacchiroli
2010-07-25 10:37 ` Romain Francoise
2010-07-25 11:39 ` Daiki Ueno [this message]
2010-07-25 12:16 ` Stefano Zacchiroli
2010-07-25 11:53 ` bug#6723: Closing Daiki Ueno
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=87wrsjhju1.fsf@broken.deisui.org \
--to=ueno@unixuser.org \
--cc=6723@debbugs.gnu.org \
--cc=romain@orebokech.com \
--cc=zack@upsilon.cc \
/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).