From: Gregory Heytings <gregory@heytings.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 57684@debbugs.gnu.org
Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair
Date: Tue, 13 Sep 2022 21:06:20 +0000 [thread overview]
Message-ID: <a993deec5894d158cbcc@heytings.org> (raw)
In-Reply-To: <CAG7BpapZdFrBPk7zDOsBJZHQ=JhD2Oaxyvy5VKDRFHg6FCyaog@mail.gmail.com>
>
> By the way, today Emacs 29 hung in Magit blaming for me, with C-g doing
> nothing. Grepping Magit sources suggest it uses the "save-restriction -
> temporarily widen" more than ten times in various places, 3 of them when
> blaming. Cannot say for sure that was it, but all the outer symptoms are
> identical with the hangs in Logview. I really think there must be a way
> to "widen no matter which locks are installed" - a lot of code seems to
> depend on that.
>
Yes, we know that, and as I said earlier it will be possible to unlock a
locked narrowing. That being said, your description is too vague to draw
a conclusion, but given that you tell that Emacs hung in Magit, I'm not
quite sure it's locked narrowing that is the culprit. Locked narrowing is
currently used only in buffers with very long lines, and only when those
buffers are on display. Files with very long lines are typically
machine-generated, and not under version control.
next prev parent reply other threads:[~2022-09-13 21:06 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 [this message]
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
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=a993deec5894d158cbcc@heytings.org \
--to=gregory@heytings.org \
--cc=57684@debbugs.gnu.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 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).