From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#44983: Truncate long lines of grep output Date: Sat, 30 Apr 2022 11:36:37 +0200 Message-ID: <87fslu6hga.fsf@gnus.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> <83tuac9j0l.fsf@gnu.org> <87tuacdpte.fsf@gnus.org> <83sfpw9gw7.fsf@gnu.org> <87levm6i0i.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19277"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: juri@linkov.net, 44983@debbugs.gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 30 11:39:43 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 1nkjZn-0004s0-5A for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 11:39:43 +0200 Original-Received: from localhost ([::1]:44462 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkjZl-0007rK-Vd for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 05:39:41 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54614) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkjXC-0004zb-8M for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 05:37:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33743) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkjXB-0004LH-VI for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 05:37:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkjXB-0003Np-Sc for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 05:37:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Apr 2022 09:37: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.165131141412990 (code B ref 44983); Sat, 30 Apr 2022 09:37:01 +0000 Original-Received: (at 44983) by debbugs.gnu.org; 30 Apr 2022 09:36:54 +0000 Original-Received: from localhost ([127.0.0.1]:55873 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkjX4-0003NR-80 for submit@debbugs.gnu.org; Sat, 30 Apr 2022 05:36:54 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:46642) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkjX2-0003ND-5P for 44983@debbugs.gnu.org; Sat, 30 Apr 2022 05:36:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=hdbp/Ut77RTW2C85hSusZHeYQA+Sn5foNCPXtZ0jPdY=; b=N8RratKCvXl0WYCshOMtivzvt0 X8sCkPqENmI5jM4ho5O24rLIzGHmbqT5/K/a1lCh+Fusd0ETDNgDmUAgMECQYBt6m5KVe03Bx4r2L 1a3Qhe7X+zFZu0HgiF/H7Kx4PVcmsOFOwQBeSnRPF/d3W2g89UCeJU4LHGOjgdP+zJvk=; Original-Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nkjWs-00067Q-7A; Sat, 30 Apr 2022 11:36:44 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAALVBMVEXm3Lvr4L3Szrnl 3cHt5svX2satrKC5wa+cj3lgZF7NqplGSEghHBWGZmb///+bgJr+AAAAAWJLR0QOb70wTwAAAAd0 SU1FB+YEHgkfFebZBakAAAGZSURBVDjLlZTPToNAEMa36gNI8Aka0pieMJB6F+y/pBdj+wBNumjP BuwLGHvw2ojUS2+S9Io22z4BcNf4Mi4wyy5CE50DJPPbb+bb2c0iVIhj+Nfrybcm1SQILQ0VoYMk LyeJM02IDEgyLDRNIycJkLNkHkamQYj+DCFvaqamHaK0lLieKvRMUZO1IjDBGO2hl0HWo5hPuyel fucZkDRucjjUoZaag5ZltW2M72CRyvJmBz+6rvussPZIBkv9uRdF0UaBuioHb6/bKNwdVYDdNiQf TMFLDRbziHgvCtsjksH84P0KP30zYHDQDYZXt2SqsE1y8HmzjGL/ugQ6p5uIxLgMLkde6MU2L8VG fjFaPpDY5oqTXBHMvMApg05jTLygQtGb3IckwKwH30dvPKMT8cv76E3sL5cDQUEsf10A4Le7nfrr RQXo+83masUAHSI/WmxhDK4MAbQosG0AunAZzi3HdhwBsPvWthoYOzBd8WgLYQhHWwwKpCpFalev luwDRm7376C2F+j/Bul7oZcBBLwhavZ60JH8AKC8MrWmlyDIAAAAJXRFWHRkYXRlOmNyZWF0ZQAy MDIyLTA0LTMwVDA5OjMxOjIxKzAwOjAwjdnyCgAAACV0RVh0ZGF0ZTptb2RpZnkAMjAyMi0wNC0z MFQwOTozMToyMSswMDowMPyESrYAAAAASUVORK5CYII= X-Now-Playing: New Order's _Everything's Gone Green_: "Everything's Gone Green" In-Reply-To: <87levm6i0i.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 30 Apr 2022 11:24:29 +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:231002 Archived-At: I've instrumented some functions to try to see what's going on. I've set things up so that grep lines that are longer than 200 chars are invisible starting at the 200th character. While the grep is running, `jit-lock-fontify-now' is called repeatedly and takes longer time each time, but with the same region: Fontifying *grep* 392-1892 Fontifying *grep* 392-1892 Fontifying *grep* 392-1892 392 is the start of the line, and 1892 is in the invisible portion of the line. That's 1500 characters, so it should be fast -- but perhaps it's extending it to the end of the line anyway? But before I start trying to debug that, I'm wondering: Why is `jit-lock-fontify-now' called at all here? There have been no display changes -- the text was inserted, but as invisible text, so no font locking should be necessary. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no