From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: gregory@heytings.org, larsi@gnus.org, 57684@debbugs.gnu.org
Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair
Date: Wed, 14 Sep 2022 14:57:11 +0300 [thread overview]
Message-ID: <83illq2mp4.fsf@gnu.org> (raw)
In-Reply-To: <CAG7BpapHhuUdzZV9cTQWac0OBiEMLiYG8u0W-dYH7cSwnX7hbQ@mail.gmail.com> (message from Paul Pogonyshev on Wed, 14 Sep 2022 11:45:01 +0200)
> From: Paul Pogonyshev <pogonyshev@gmail.com>
> Date: Wed, 14 Sep 2022 11:45:01 +0200
> Cc: Gregory Heytings <gregory@heytings.org>, Lars Ingebrigtsen <larsi@gnus.org>, 57684@debbugs.gnu.org
>
> By the way, it would really be nice if Emacs could do something about hangs irrespective of what causes
> that. Even if Elisp code is buggy, Emacs itself should never allow it to fall into an infinite loop and stop
> responding to C-g, leaving full restart as the only way out.
I think that's impossible in general, unless we restrict what Lisp
programs can do. Every programming language can be used to write a
buggy program.
However, it should be possible to prevent some cases of such
problematic behavior, certainly so when the infloop is caused by our
bug. But for that we need to know the details of the specific case in
order to investigate.
next prev parent reply other threads:[~2022-09-14 11:57 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 [this message]
2022-09-16 3:38 ` Richard Stallman
2022-09-16 6:04 ` Eli Zaretskii
2022-09-17 3:40 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83illq2mp4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57684@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=pogonyshev@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 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.