From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44134@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>,
Stephen Berman <stephen.berman@gmx.net>
Subject: bug#44134: What is the conclusion on epa-list-keys?
Date: Sat, 16 Jan 2021 13:15:52 +0530 [thread overview]
Message-ID: <m2a6t92ukv.fsf@codeisgreat.org> (raw)
In-Reply-To: <87d003b74g.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 24 Nov 2020 07:29:03 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> I think the problem is due to [1: 517285f7cae] (Ccing Lars who who wrote
>> that commit) which dropped the epa-list-keys text property from
>> epa--insert-keys. So it would be safer to restore that property rather
>> than switching to detect the epa-key property as in your patch.
>
> Yes, I think the property was dropped by mistake in my patch.
Lars, I am not sure if you have restored the changes. If you have
already done then this bug was not due to that.
I am still seeing issue. i.e. after quiting the buffer with ‘q‘ key, I
cannot list the keys with ‘M-x epa-list-keys‘ again. Same behaviour as
in my original bug-report.
next prev parent reply other threads:[~2021-01-16 7:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 4:58 bug#44134: 28.0.50; epa-list-keys failing with ‘wrong type argument: interger-or-marker-p, nil’ Pankaj Jangid
2020-10-22 8:23 ` Colin Baxter
2020-10-22 8:49 ` Stephen Berman
2020-10-22 11:05 ` Colin Baxter
2020-10-22 11:35 ` Stephen Berman
2020-10-22 14:21 ` Colin Baxter
2020-10-22 16:01 ` Stephen Berman
2020-10-22 17:29 ` Colin Baxter
2020-11-22 6:38 ` bug#44134: What is the conclusion on epa-list-keys? Pankaj Jangid
2020-11-22 10:17 ` Stephen Berman
2020-11-23 19:22 ` Noam Postavsky
2020-11-24 6:29 ` Lars Ingebrigtsen
2021-01-16 7:45 ` Pankaj Jangid [this message]
2021-01-18 16:31 ` Lars Ingebrigtsen
2021-01-18 16:36 ` Lars Ingebrigtsen
2021-01-19 4:06 ` Pankaj Jangid
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=m2a6t92ukv.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=44134@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=stephen.berman@gmx.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.
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).