unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 74630@debbugs.gnu.org
Subject: bug#74630: 31.0.50; emacs-mail-verify
Date: Wed, 04 Dec 2024 15:26:15 +0200	[thread overview]
Message-ID: <864j3j1sw8.fsf@gnu.org> (raw)
In-Reply-To: <E1tIiZN-0001hB-LT@fencepost.gnu.org> (message from Richard Stallman on Wed, 04 Dec 2024 01:09:05 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: 74630@debbugs.gnu.org
> Date: Wed, 04 Dec 2024 01:09:05 -0500
> 
>   > Not sure what you expected the doc string to say.  Would the below be
>   > enough?
> 
>   >   Verify OpenPGP cleartext signed messages in the current buffer.
>   >   The buffer is expected to contain a mail message.
> 
>   >   If the verification fails, the command signals an error.
> 
> That is better, becauee it gives enough information to deduce what
> indicates success.  But the user should need to do any deduction about
> that, let alone read code and guess what some other functions do.

Thanks, I installed a change along those lines.

> To make the doc string truly clear, it should say explicitly what
> indicates success.  That way the user can know, rather than just
> supposing.

I don't know how to describe success in this case, except as the lack
of an error.

> Should the function be changed to display a message, "Signature verified",
> on success?

It says "Verifying...done", which I think is enough (and quite
standard in Emacs).

> Do some people run this function from a hook for every message and
> want to see output only in case of failure?

See above: it displays a message in case of success as well.

> Should it a value indicating success or failure?

I don't know.  The values of the relevant functions don't seem to be
documented.





      reply	other threads:[~2024-12-04 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01  5:39 bug#74630: 31.0.50; emacs-mail-verify Richard Stallman
2024-12-01 12:53 ` Eli Zaretskii
2024-12-04  6:09   ` Richard Stallman
2024-12-04 13:26     ` Eli Zaretskii [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=864j3j1sw8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74630@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).