From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57684@debbugs.gnu.org
Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair
Date: Fri, 16 Sep 2022 23:40:19 -0400 [thread overview]
Message-ID: <E1oZOgl-00080D-M6@fencepost.gnu.org> (raw)
In-Reply-To: <83sfkr4zyr.fsf@gnu.org> (message from Eli Zaretskii on Fri, 16 Sep 2022 09:04:28 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> It is still true. The problem exists only with Lisp code that is run
> when QUITs are either intentionally disabled, or when Lisp is run from
> the display engine, where QUIT is caught and basically ignored. The
> particular case which started this thread is of the latter variety.
I never allowed redisplay to run Lisp code -- it seemed very dangerous.
An error there could leave redisplay data structures inconsistent.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-09-17 3:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 19:37 bug#57684: locked narrowing breaks existing code without an apparent way to repair Paul Pogonyshev
2022-09-08 19:57 ` Gregory Heytings
2022-09-08 20:30 ` Paul Pogonyshev
2022-09-09 1:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-09 16:16 ` Lars Ingebrigtsen
2022-09-09 16:20 ` Gregory Heytings
2022-09-13 20:54 ` Paul Pogonyshev
2022-09-13 21:06 ` Gregory Heytings
2022-09-13 21:13 ` Paul Pogonyshev
2022-09-13 21:35 ` Gregory Heytings
2022-09-14 2:34 ` Eli Zaretskii
2022-09-14 9:45 ` Paul Pogonyshev
2022-09-14 11:57 ` Eli Zaretskii
2022-09-16 3:38 ` Richard Stallman
2022-09-16 6:04 ` Eli Zaretskii
2022-09-17 3:40 ` Richard Stallman [this message]
2022-09-17 6:33 ` Eli Zaretskii
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=E1oZOgl-00080D-M6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=57684@debbugs.gnu.org \
--cc=eliz@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).