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:15:07 +0300 Message-ID: <83mtg298t0.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> <83tuac9j0l.fsf@gnu.org> <87tuacdpte.fsf@gnus.org> <83sfpw9gw7.fsf@gnu.org> <87levm6i0i.fsf@gnus.org> <87fslu6hga.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28578"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, 44983@debbugs.gnu.org, dgutov@yandex.ru To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 30 12:16:32 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 1nkk9Q-0007LZ-FA for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 12:16:32 +0200 Original-Received: from localhost ([::1]:55164 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nkk9P-0000BU-1l for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Apr 2022 06:16:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58524) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkk8x-0000BD-25 for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:16:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33791) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nkk8w-0000ug-Ar for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:16:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nkk8v-0004Nc-P5 for bug-gnu-emacs@gnu.org; Sat, 30 Apr 2022 06:16:02 -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:16: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.165131371416782 (code B ref 44983); Sat, 30 Apr 2022 10:16:01 +0000 Original-Received: (at 44983) by debbugs.gnu.org; 30 Apr 2022 10:15:14 +0000 Original-Received: from localhost ([127.0.0.1]:55921 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkk89-0004MX-Tk for submit@debbugs.gnu.org; Sat, 30 Apr 2022 06:15:14 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36900) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nkk88-0004MH-9w for 44983@debbugs.gnu.org; Sat, 30 Apr 2022 06:15:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42230) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nkk7z-0000Wb-R2; Sat, 30 Apr 2022 06:15:04 -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=COIaC8McigieTTKqvX2ICWuIBZRnPIjCAPl+yO7ck3s=; b=FMRO3OxPaJQW a5uFmKDqGVe6vrpeO+FBQn/SCdC6WW/fErP53x2cZ1Du3nakQV6G5dUOZxHiiuwssNu9iolpU03Ra nUWpTp9bXzYoaQWyiNJjE49DAZC6iu7iED/4x331AZgHoTFFsmKyfo+FboFMj8VkBP/qdEH38pG5C K3M5BH5TwzfMHlR53kBeaX9uFonF/224Ini75s+WXsomHEvVbBqgSNYii5ZoLMFOnVnorh2JOX8x0 s1QyCcv8mkShIw0+tadDgMJNUrzZJIIMPifpPZ6pRyQ9EmxdynmhooFWXlpdAdFugSccwE6n9C6vT vz7i5lrTwt3HG/rEXunjew==; Original-Received: from [87.69.77.57] (port=4510 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 1nkk7z-00052h-9D; Sat, 30 Apr 2022 06:15:03 -0400 In-Reply-To: <87fslu6hga.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 30 Apr 2022 11:36:37 +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:231008 Archived-At: > From: Lars Ingebrigtsen > Cc: juri@linkov.net, 44983@debbugs.gnu.org, dgutov@yandex.ru > Date: Sat, 30 Apr 2022 11:36:37 +0200 > > 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. Are you saying that buffer position 392 was in invisible text? If so, jit-lock-fontify-now should not have been called. But if position 392 is visible, then what you see is expected: the buffer text has changed, and therefore redisplay will arrange to redisplay the buffer. Part of redisplaying the buffer is making sure the text that might wind up on display is fontified. Which part will actually be on display can only be known _after_ the text is fontified (because fontification can change faces, and thus affect what's visible in the window). So we always fontify the 500-character chunk, per jit-lock.el's defaults. Did I answer your question?