all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 44134@debbugs.gnu.org, Pankaj Jangid <pankaj@codeisgreat.org>,
	Stephen Berman <stephen.berman@gmx.net>
Subject: bug#44134: What is the conclusion on epa-list-keys?
Date: Tue, 24 Nov 2020 07:29:03 +0100	[thread overview]
Message-ID: <87d003b74g.fsf@gnus.org> (raw)
In-Reply-To: <85360zkhdp.fsf@gmail.com> (Noam Postavsky's message of "Mon, 23 Nov 2020 14:22:42 -0500")

Noam Postavsky <npostavs@gmail.com> 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.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-11-24  6:29 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 [this message]
2021-01-16  7:45         ` Pankaj Jangid
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d003b74g.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44134@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=pankaj@codeisgreat.org \
    --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 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.