From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 43704@debbugs.gnu.org
Subject: bug#43704: 26.1: gpg error on passphrase typo
Date: Tue, 29 Sep 2020 16:37:49 +0200 [thread overview]
Message-ID: <87zh58bqde.fsf@gnus.org> (raw)
In-Reply-To: <20200929131635.ia4tpjlfvxbd3yys@E15-2016.optimum.net> (Boruch Baum's message of "Tue, 29 Sep 2020 09:16:35 -0400")
Boruch Baum <boruch_baum@gmx.com> writes:
> When making a mistake typing a gpg passphrase, an 'error' is generated,
> instead of a 'user-error'. The significance of the difference is that if
> the user has enabled 'toggle-debug-on-error', the typo generates an
> annoying backtrace buffer that then needs to be killed, followed by a
> window navigation to the gpg buffer in use.
Is this the backtrace you get?
Debugger entered--Lisp error: (file-missing "Opening input file" "Decryption failed" "")
signal(file-missing ("Opening input file" "Decryption failed" ""))
epa-file--find-file-not-found-function()
run-hook-with-args-until-success(epa-file--find-file-not-found-function)
find-file-noselect-1(#<killed buffer> "/tmp/foo.gpg" nil nil "/tmp/foo.gpg" (24379592 66306))
find-file-noselect("/tmp/foo.gpg" nil nil t)
find-file("/tmp/foo.gpg" t)
funcall-interactively(find-file "/tmp/foo.gpg" t)
call-interactively(find-file nil nil)
command-execute(find-file)
I'm not sure whether there's any way for epa to know at this point
whether the failure was due to a wrong password or something else, so
I'm not sure a user-error would be appropriate. Anybody know?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-29 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 13:16 bug#43704: 26.1: gpg error on passphrase typo Boruch Baum
2020-09-29 13:41 ` Andreas Schwab
2020-09-29 13:55 ` Boruch Baum
2020-09-29 14:37 ` Lars Ingebrigtsen [this message]
2020-09-29 14:41 ` Lars Ingebrigtsen
2020-09-30 1:48 ` Lars Ingebrigtsen
2020-09-30 6:33 ` Boruch Baum
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=87zh58bqde.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43704@debbugs.gnu.org \
--cc=boruch_baum@gmx.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.