GNU bug report logs - #56393
Actually fix the long lines display bug

Previous Next

Full log

Message #539 received at 56393 <at> debbugs.gnu.org (full text, mbox):

From: Gregory Heytings <gregory <at> heytings.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: gerd.moellmann <at> gmail.com, Eli Zaretskii <eliz <at> gnu.org>,
 56393 <at> debbugs.gnu.org
Subject: Re: bug#56393: Actually fix the long lines display bug
Date: Tue, 19 Jul 2022 14:24:07 +0000

>
> Do you need it to run as often as the current code does?  It's a 
> heuristic -- if it gets it wrong in some pathological situation (i.e., 
> if the user replaces all newlines with spaces in a huge buffer with a 
> function that does just that), that's not a deal breaker.
>

I think you need, yes.  And with the present heuristic it will not run 
that often, in fact.  The problem is that a single editing operation like 
C-u 100000 a creates a long line, and Emacs would start choking again. 
Or C-x i <a file with long lines>.  Or a shell process which produces a 
long line.  And so forth.

>
> That is, I don't think you have to run the detection as often as you do 
> now.  If the previous call said you had no lines longer than 80 
> characters, you don't have to run it again until the buffer has grown 
> more than 30K characters, or you have a modiff in the thousands region.
>

Hmmm...  Thanks, I'll see if I can do something with that idea.

Previous Next

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