unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 drew.adams@oracle.com,  larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: [External] : Re: master 513c5d827d: Use `format-prompt' in
Date: Wed, 07 Sep 2022 12:03:48 +0200	[thread overview]
Message-ID: <87tu5jbiwr.fsf@gmail.com> (raw)
In-Reply-To: <E1oVkiV-0004B3-1h@fencepost.gnu.org> (Richard Stallman's message of "Tue, 06 Sep 2022 22:23:03 -0400")

>>>>> On Tue, 06 Sep 2022 22:23:03 -0400, Richard Stallman <rms@gnu.org> said:

    Richard> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
    Richard> [[[ whether defending the US Constitution against all enemies,     ]]]
    Richard> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]

    >> Not only that.  The readability is also diminished.  Compare

    >> (read-char-by-name
    >> "Unicode name, single char, or hex, default all: " t))

    >> with

    >> (read-char-by-name
    >> (format-prompt "Unicode name, single char, or hex" "all")
    >> t)

    >> To me, the first one tells very accurately what will the user see as
    >> the prompt, while the second doesn't.

    Richard> To be fair, the two arguments of `format-prompt' have a clear semantic
    Richard> distinction.  The first is the general description of the argument to
    Richard> be read, and the second is its default value.

Yes. What this particular instance obscures is that the second argument
is generally not a literal string, but a variable, so any general
translation could only be applied to the first argument. Also:

    (format-prompt PROMPT DEFAULT &rest FORMAT-ARGS)

so that also applies to all the FORMAT-ARGS.

Robert
-- 



      reply	other threads:[~2022-09-07 10:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03  9:15 master 513c5d827d: Use `format-prompt' in Eli Zaretskii
2022-09-03  9:22 ` Lars Ingebrigtsen
2022-09-03  9:38   ` Eli Zaretskii
2022-09-03  9:45     ` Lars Ingebrigtsen
2022-09-03  9:56       ` Eli Zaretskii
2022-09-03 15:50       ` [External] : " Drew Adams
2022-09-05  4:04         ` Richard Stallman
2022-09-05  8:26           ` Robert Pluim
2022-09-05 11:42             ` Eli Zaretskii
2022-09-05 11:54               ` Robert Pluim
2022-09-05 12:19                 ` Eli Zaretskii
2022-09-05 12:29                   ` Robert Pluim
2022-09-05 12:33                     ` Eli Zaretskii
2022-09-05 16:02                       ` Gregory Heytings
2022-09-05 16:10                         ` Robert Pluim
2022-09-06  4:16               ` Richard Stallman
2022-09-06 12:37                 ` Eli Zaretskii
2022-09-07  2:23                   ` Richard Stallman
2022-09-07 10:03                     ` Robert Pluim [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=87tu5jbiwr.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).