GNU bug report logs - #57684
locked narrowing breaks existing code without an apparent way to repair

Previous Next

Full log

View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Paul Pogonyshev <pogonyshev <at> gmail.com>
Cc: Gregory Heytings <gregory <at> heytings.org>, 57684 <at> 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

Paul Pogonyshev <pogonyshev <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.