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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
Subject: bug#56393: Actually fix the long lines display bug
Date: Mon, 18 Jul 2022 20:19:28 +0300

> Date: Mon, 18 Jul 2022 17:11:23 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: gerd.moellmann <at> gmail.com, larsi <at> gnus.org, 56393 <at> debbugs.gnu.org
> 
> > M-x toggle-truncate-lines RET
> 
> BTW, there is now a C-x x t binding for that.

Old habits die hard ;-)  Besides, what I really type is

  M-x tog TAB tr TAB RET

> > Now simple cursor motion commands that use redisplay optimizations are 
> > fast, but commands that cause more thorough redisplay are as slow as on 
> > master.  As a simple example, try just "M-x" and wait until the "M-x" 
> > prompt appears in the minibuffer -- here it takes much longer, basically 
> > as long as the version on master.
> >
> 
> Yes, it's a font locking issue.  Turn font-lock-mode off and the problem 
> is gone.  As I said, I'll look at that later.

So you are saying that font-lock becomes much more expensive when
lines are truncated?  Because the comparison is with the same file and
font-lock turned ON, but without line truncation.

Previous Next

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