From: Steven Allen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 71525@debbugs.gnu.org
Subject: bug#71525: 30.0.50; Spin in delete-region/interval_deletion_adjustment Spin in delete-region/interval_deletion_adjustment)
Date: Thu, 13 Jun 2024 12:42:02 -0700 [thread overview]
Message-ID: <87sexgd3zp.fsf@stebalien.com> (raw)
In-Reply-To: <08b9b04d-7c6e-20ed-89ec-4d74f345704d@gmail.com>
Jim Porter <jporterbugs@gmail.com> writes:
> It sounds like we've found the culprit, but I am tracking this and can
> help fix/update Eshell if that's the way we decide to go. (I haven't
> read through all of bug#66020 yet so I don't fully understand all of the
> changes there, and can't yet say where the fix should be.)
From what I can tell, it's not Eshell, just triggered by Eshell. It
appears that Emacs locks up _inside_ the C code and never leaves (not
even `C-g` works).
I believe I reproduced this once with `jinx` calling
`next-single-char-property-change` in a non-eshell buffer. At the very
least, it locked up in the same way (right after I tried to delete a
buffer). But I'm not sure how that would have interacted with the
process output code.
next prev parent reply other threads:[~2024-06-13 19:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 19:20 bug#71525: 30.0.50; Spin in delete-region/interval_deletion_adjustment Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <handler.71525.B.171822007123849.ack@debbugs.gnu.org>
2024-06-13 5:14 ` bug#71525: Acknowledgement (30.0.50; Spin in delete-region/interval_deletion_adjustment) Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-13 5:52 ` bug#71525: 30.0.50; Spin in delete-region/interval_deletion_adjustment " Eli Zaretskii
2024-06-13 15:32 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-13 15:52 ` Eli Zaretskii
2024-06-13 16:00 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-13 16:06 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-13 16:31 ` Eli Zaretskii
2024-06-13 21:47 ` Dmitry Gutov
2024-06-13 23:41 ` Dmitry Gutov
2024-06-14 7:13 ` Eli Zaretskii
2024-06-14 16:51 ` Dmitry Gutov
2024-06-14 18:14 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-14 18:17 ` Dmitry Gutov
2024-06-14 18:46 ` Eli Zaretskii
2024-06-14 19:13 ` Dmitry Gutov
2024-06-13 19:18 ` Jim Porter
2024-06-13 19:42 ` Steven Allen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-13 5:49 ` bug#71525: 30.0.50; Spin in delete-region/interval_deletion_adjustment 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=87sexgd3zp.fsf@stebalien.com \
--to=bug-gnu-emacs@gnu.org \
--cc=71525@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=steven@stebalien.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).