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 13:02:59 +0200 Message-ID: <87r15e4yvw.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> <87bkwi6h9l.fsf@gnus.org> <874k2a6gjo.fsf@gnus.org> <83o80i992v.fsf@gnu.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="7751"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: dgutov@yandex.ru, 44983@debbugs.gnu.org, juri@linkov.net To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 30 13:04:20 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 1nkktg-0001l3-EQ for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 13:04:20 +0200 Original-Received: from localhost ([::1]:44490 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkkte-0006H6-Lz for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 07:04:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35958) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkktO-0006D7-K1 for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 07:04:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33833) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkktO-0007gJ-AV for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 07:04:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkktO-0005l3-70 for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 07:04:02 -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 11:04:02 +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.165131659022069 (code B ref 44983); Sat, 30 Apr 2022 11:04:02 +0000 Original-Received: (at 44983) by debbugs.gnu.org; 30 Apr 2022 11:03:10 +0000 Original-Received: from localhost ([127.0.0.1]:55963 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkksY-0005jt-E2 for submit@debbugs.gnu.org; Sat, 30 Apr 2022 07:03:10 -0400 Original-Received: from quimby.gnus.org ([95.216.78.240]:47108) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkksW-0005jd-Hh for 44983@debbugs.gnu.org; Sat, 30 Apr 2022 07:03:09 -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=/RprUk1uMRPQqtS//oHa67mwpiNTloFzPNVLxGVtse0=; b=ZxLUTnNpUP7fOS+xT+tq/Elfqy 8+KIc/Xj26fnrZPlwQ9AEh5hM5m0YQndJ48mtg754xQIbTbJaU4INdMEI0uWLJ07r8Ye5TTrlYQyY r3YSLjO8AAETwlbcHEk7Haza1qUE+1uROLrlhuXBXh0l3gL4HVj+peMfirX7DrK1kzt8=; 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 1nkksN-00073l-ML; Sat, 30 Apr 2022 13:03:01 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAElBMVEX8+/uopaMnJCTS 0M6Cfnz////M28vfAAAAAWJLR0QF+G/pxwAAAAd0SU1FB+YEHgo5F8lPWfgAAAFqSURBVDjLdZOB kYQgDEXjYQGgFLDEFABiAQtn/zVdQGTB5ZidWSeP8JNPAChrwc+y4NUdh9gALYW+40cTR4dBjxLQ CjxLXLRxlLqCqQOR1A3mDpwU7qp++qMO/C1gf4J1mHGShDGobT/A6v8BBx0wKpeWuBQR3TlC4Zje KWyX7iAGcwJTxMei/VwsaPxaNCMB4AD4SdgRME5rCd1OPvdAkuxcBwxfl4lorVZrp0FzMPzjtlIT nd2TFSwLhxUNOCNu2TyhYqcRWPZdJsC6JiNodKRyjoe2jxBJRAzf4EQDZTgcH1YBIW7gUk1Jvu+D pefXNZh9H7w70qXRAcrjZbPGA6TR3lIfq7cdyCORJHwH3HX3pfumD7vmf67LrQ2Ixu75Y2MJJysg f9pYpNZcV9nPPpdXRUJCtWSb4ru+kWTLbeILdlPfZwblojZ+zrEC+ckwzbQTNBpmaQGXpAYjypYp JQfAZIUB2C6r/gB9NXonsqP/TwAAACV0RVh0ZGF0ZTpjcmVhdGUAMjAyMi0wNC0zMFQxMDo1Nzoy MyswMDowMOV3srkAAAAldEVYdGRhdGU6bW9kaWZ5ADIwMjItMDQtMzBUMTA6NTc6MjMrMDA6MDCU KgoFAAAAAElFTkSuQmCC X-Now-Playing: New Order's _Low-Life (1)_: "Sunrise" In-Reply-To: <83o80i992v.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Apr 2022 13:09:12 +0300") 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:231011 Archived-At: Eli Zaretskii writes: > 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. Yes, that's correct, I think. But shouldn't it be smarter here? That is, the display engine does know that all the text it inserted was invisible, so calling jit-lock again (with the same parameters as previous time) is futile. However, this is probably not something many modes do, so putting more effort into optimising this is probably not worth it. > 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. Probably. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no