From: Eli Zaretskii <eliz@gnu.org>
To: Gabriele Nicolardi <gabriele@medialab.sissa.it>,
Stefan Kangas <stefankangas@gmail.com>
Cc: 71429@debbugs.gnu.org
Subject: bug#71429: Inconsistent y-or-n-p prompt behavior in Emacs Lisp
Date: Sat, 08 Jun 2024 11:24:50 +0300 [thread overview]
Message-ID: <86bk4bet9p.fsf@gnu.org> (raw)
In-Reply-To: <0a72f9c4-3f1c-4fc8-a412-169dca892b57@medialab.sissa.it> (message from Gabriele Nicolardi on Sat, 8 Jun 2024 09:03:37 +0200)
> Date: Sat, 8 Jun 2024 09:03:37 +0200
> From: Gabriele Nicolardi <gabriele@medialab.sissa.it>
>
> I have the following Emacs Lisp code:
>
> (progn
> (y-or-n-p "Test: ")
> (let ((search-spaces-regexp "\\(?:\\n?[\s\t]+\\|\n\\)?"))
> (y-or-n-p "Test: ")))
>
> The first prompt from the y-or-n-p function appears as expected:
>
> Test: (y or n)
>
> However, the second prompt appears differently:
>
> Test: (‘y’ or ‘n’)
>
> I’m trying to understand why the second prompt format changes. What causes this inconsistency in the
> y-or-n-p prompt?
>
> I suspect it might be related to the search-spaces-regexp variable or how Emacs handles interactive
> prompts, but I’m not sure. Any insights or explanations would be greatly appreciated!
Stefan, can you please look into this? It sounds like some issue with
substitute-command-keys:
(substitute-command-keys "(\\`y' or \\`n') ")
=> #("(y or n) " 1 2 (font-lock-face help-key-binding face help-key-binding) 6 7 (font-lock-face help-key-binding face help-key-binding))
But
(let ((search-spaces-regexp "\\(?:\\n?[\s\t]+\\|\n\\)?"))
(substitute-command-keys "(\\`y' or \\`n') "))
=> "(\\‘y’ or \\‘n’) "
I actually don't understand why we use \\`y' and \\`n' in y-or-n-p.
Why those backslashes, and not just `y' and `n'? That's your change
in commit a36ecc408a. If I remove the backslashes, the results are
identical whether or not search-spaces-regexp is let-bound.
next prev parent reply other threads:[~2024-06-08 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 7:03 bug#71429: Inconsistent y-or-n-p prompt behavior in Emacs Lisp Gabriele Nicolardi
2024-06-08 8:24 ` Eli Zaretskii [this message]
2024-06-08 9:20 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 13:59 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 14:58 ` Eli Zaretskii
2024-06-08 15:30 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 15:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 16:36 ` Eli Zaretskii
2024-06-08 17:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 18:08 ` Eli Zaretskii
2024-06-09 11:02 ` Stefan Kangas
2024-06-08 15:47 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 16:44 ` Eli Zaretskii
2024-06-09 11:01 ` Stefan Kangas
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=86bk4bet9p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71429@debbugs.gnu.org \
--cc=gabriele@medialab.sissa.it \
--cc=stefankangas@gmail.com \
/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).