unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>,  34726@debbugs.gnu.org
Subject: bug#34726: epa-insert-keys
Date: Wed, 26 Aug 2020 13:21:42 +0200	[thread overview]
Message-ID: <87d03d1wl5.fsf@gnus.org> (raw)
In-Reply-To: <m2ftrzf2qx.fsf@gmail.com> (Robert Pluim's message of "Thu, 07 Mar 2019 10:33:10 +0100")

Robert Pluim <rpluim@gmail.com> writes:

>     rms> I think we should include a cleaned-up and clarified version
>     rms> of this table in those two commands' doc strings.
>
> Thatʼs not a path Iʼd want to go down. The gpg documentation is long
> and complex, because itʼs a complex program. Attempting to summarise
> it in a few docstrings will result in incomplete or possibly incorrect
> information, Iʼd rather people read the original.

That's true, but epg already does an interpretation of those status
characters and then fontifies the buffer based on them:

(defvar epg-key-validity-alist
  '((?o . unknown)
    (?i . invalid)
    (?d . disabled)
    (?r . revoked)
    (?e . expired)
    (?- . none)
    (?q . undefined)
    (?n . never)
    (?m . marginal)
    (?f . full)
    (?u . ultimate)))

To not then actually tell the users what we've interpreted the
characters to means just seems odd.

I've now changed this in Emacs 28 so that hovering over the character
says what the validity is (i.e., the help-echo property).

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





      parent reply	other threads:[~2020-08-26 11:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  3:27 bug#34726: epa-insert-keys Richard Stallman
2019-03-05 16:08 ` Eli Zaretskii
2019-03-06  2:15   ` Richard Stallman
2019-03-06 10:27     ` Robert Pluim
2019-03-07  3:38       ` Richard Stallman
2019-03-07  9:33         ` Robert Pluim
2019-03-08  4:14           ` Richard Stallman
2019-03-08  8:19             ` Eli Zaretskii
2019-03-09  3:19               ` Richard Stallman
2020-08-26 11:21           ` Lars Ingebrigtsen [this message]

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=87d03d1wl5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34726@debbugs.gnu.org \
    --cc=rms@gnu.org \
    /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).