From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#44983: Truncate long lines of grep output Date: Sat, 30 Apr 2022 13:09:12 +0300 Message-ID: <83o80i992v.fsf@gnu.org> References: <87v9dlc3ti.fsf_-_@mail.linkov.net> <83ft4pik35.fsf@gnu.org> <87sg8p5kw0.fsf@mail.linkov.net> <83eek8hoyx.fsf@gnu.org> <87h7p4r1n9.fsf@mail.linkov.net> <87tuacf79e.fsf@gnus.org> <87bkwi6h9l.fsf@gnus.org> <874k2a6gjo.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4297"; mail-complaints-to="usenet@ciao.gmane.io" Cc: dgutov@yandex.ru, 44983@debbugs.gnu.org, juri@linkov.net To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 30 12:11:06 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nkk4A-0000zf-2f for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 12:11:06 +0200 Original-Received: from localhost ([::1]:54524 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkk48-0007nL-MB for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 06:11:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58126) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkk3A-0007n6-PO for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:10:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33785) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkk38-0008Jz-7P for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:10:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkk37-0004Ed-SN for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:10:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Apr 2022 10:10:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 44983 X-GNU-PR-Package: emacs Original-Received: via spool by 44983-submit@debbugs.gnu.org id=B44983.165131335616221 (code B ref 44983); Sat, 30 Apr 2022 10:10:01 +0000 Original-Received: (at 44983) by debbugs.gnu.org; 30 Apr 2022 10:09:16 +0000 Original-Received: from localhost ([127.0.0.1]:55915 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkk2O-0004DZ-7G for submit@debbugs.gnu.org; Sat, 30 Apr 2022 06:09:16 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36552) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkk2M-0004DM-Lp for 44983@debbugs.gnu.org; Sat, 30 Apr 2022 06:09:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42160) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkk2H-0008HA-0M; Sat, 30 Apr 2022 06:09:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=kr3Uwb+YlPxAkoliKThQbLG3ZVGT+N5li5L3Lt6zH6o=; b=CIVhC8xXBZom qWFu1dls0FsMtfbpdSQtqiG7AE1VsCa7tvt2+/aNrkuontZMhMaZz97MYFqD8UK2Udbclx1Ln9yuY hM8SOoZEjn71hFvLnI/ap5AgvDADnpoOZIcZnq+vyI8kXXKflP4ZNDStEH9fYimLvRdbBnNne6OGS NDPs1EssaezrrdR45W/LRGdC9um/NPDEaY5rXKf98sxlRRUmTIChQwxowHoycgdg+qTkyYv7JbdxR rtU88UHqbGRcrkBob2w3O0HLCn98ntJ2NUq7M4EG4V2PsZGqOROjo0DhTzmBCkCot+SESyk5ncKop Cfs/LslxbN7bh6fwxtPPnw==; Original-Received: from [87.69.77.57] (port=4148 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkk2G-0004X9-EV; Sat, 30 Apr 2022 06:09:08 -0400 In-Reply-To: <874k2a6gjo.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 30 Apr 2022 11:56:11 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:231007 Archived-At: > From: Lars Ingebrigtsen > Date: Sat, 30 Apr 2022 11:56:11 +0200 > Cc: 44983@debbugs.gnu.org, Juri Linkov > > 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.