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@gmx.net, stefankangas@gmail.com
Subject: bug#71429: Inconsistent y-or-n-p prompt behavior in Emacs Lisp
Date: Sat, 08 Jun 2024 13:41:14 -0400 [thread overview]
Message-ID: <jwv1q57pc79.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86wmmzbddb.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 08 Jun 2024 19:36:32 +0300")
> Or maybe you are saying that a Lisp program that binds
> search-spaces-regexp has a bug, because Lisp code is not supposed to
> bind that?
That, yes. Binding it should be done carefully only at those places
where the contained Lisp code is performing a search whose regexp was
built from interactive user input.
If you let bind that var and then call arbitrary code, I'd
expect breakage.
Stefan
next prev parent reply other threads:[~2024-06-08 17:41 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv1q57pc79.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.