From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: Gregory Heytings <gregory@heytings.org>, 57684@debbugs.gnu.org
Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair
Date: Fri, 09 Sep 2022 09:46:44 +0800 [thread overview]
Message-ID: <87o7vp720r.fsf@yahoo.com> (raw)
In-Reply-To: <CAG7BpaoZ859OhBx6ZcpVAgWVjFqug+CDG0ZRP6wi0A08N7h5qg@mail.gmail.com> (Paul Pogonyshev's message of "Thu, 8 Sep 2022 22:30:45 +0200")
Paul Pogonyshev <pogonyshev@gmail.com> writes:
> Good to hear. I think in all cases it should be left to the coder to
> temporarily lift restrictions, even if those are "locked", maybe
> with strong warnings in documentation. Speed should always
> come a second priority to functionality. Besides, Logview (one
> example of what would suffer if widening is impossible) is very
> fast.
>
> As an example of why widening might be needed: fontification
> may depend on preceding text in the buffer. Maybe standard
> Emacs fontification code handles that separately, but e.g.
> Logview (almost) completely replaces the standard code here
> with a home-grown solution aimed specifically at log files. And
> actually this was done exactly for speed.
>
> Anyway, I hope this is finished soon.
For the time being, you can either use an indirect buffer, or run the
fontification code in a timer.
The former already exists in the wild.
next prev parent reply other threads:[~2022-09-09 1:46 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 [this message]
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
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=87o7vp720r.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57684@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=luangruo@yahoo.com \
--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).