GNU bug report logs - #44983
Truncate long lines of grep output

Previous Next

Package: emacs;

Reported by: Juri Linkov <juri <at> linkov.net>

Date: Tue, 1 Dec 2020 08:56:01 UTC

Severity: normal

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: juri <at> linkov.net, 44983 <at> debbugs.gnu.org, dgutov <at> yandex.ru
Subject: Re: bug#44983: Truncate long lines of grep output
Date: Sat, 30 Apr 2022 13:09:12 +0300
> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Sat, 30 Apr 2022 11:56:11 +0200
> Cc: 44983 <at> debbugs.gnu.org, Juri Linkov <juri <at> linkov.net>
> 
> But I guess the real question here is still why we're font-locking
> invisible text.

We are not.  The display engine will never call jit-lock on a region
that starts in invisible text.  But a region that starts in visible
text can end in invisible text, and font-lock doesn't pay attention to
invisibility spec, AFAIR, it just looks at the buffer text
disregarding everything else.

For me, the more important question is: why the problem didn't
disappear when you turned off font-lock-mode in the offending buffer.
And I think I know why: you need to turn off jit-lock-mode as well.




This bug report was last modified 3 years and 19 days ago.

Previous Next


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