unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gabriele@medialab.sissa.it, 71429@debbugs.gnu.org,
	Stephen Berman <stephen.berman@gmx.net>,
	stefankangas@gmail.com
Subject: bug#71429: Inconsistent y-or-n-p prompt behavior in Emacs Lisp
Date: Sat, 08 Jun 2024 11:38:53 -0400	[thread overview]
Message-ID: <jwvcyorphv7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <861q57cwhi.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Jun 2024 17:58:17 +0300")

> Thanks.  To me, this means that key-valid-p should bind
> search-spaces-regexp to nil, because otherwise the value will subvert
> its contract.  Do you agree?

I kind of agree, but I wonder why it would be non-nil at this point.
AFAIK `search-spaces-regexp` is meant for interactive searches, so
let-binding it around code like `substitute-command-keys`,
`split-string`, or `key-valid-p` sounds like a bug.


        Stefan






  parent reply	other threads:[~2024-06-08 15:38 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
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 [this message]
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=jwvcyorphv7.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71429@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gabriele@medialab.sissa.it \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    --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 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).