From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#25672: Font-locking issues when font-lock-fontified is nil Date: Wed, 30 Oct 2019 17:07:10 +0100 Message-ID: <877e4mrzdd.fsf@gnus.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="19929"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 25672@debbugs.gnu.org To: =?UTF-8?Q?Cl=C3=A9ment?= Pit--Claudel Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Oct 30 17:08:20 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPqWB-00053R-NB for geb-bug-gnu-emacs@m.gmane.org; Wed, 30 Oct 2019 17:08:19 +0100 Original-Received: from localhost ([::1]:42314 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPqWA-0002e2-Jj for geb-bug-gnu-emacs@m.gmane.org; Wed, 30 Oct 2019 12:08:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52322) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPqVx-0002aN-0R for bug-gnu-emacs@gnu.org; Wed, 30 Oct 2019 12:08:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPqVv-00008V-LW for bug-gnu-emacs@gnu.org; Wed, 30 Oct 2019 12:08:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42490) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iPqVv-00007O-Ba for bug-gnu-emacs@gnu.org; Wed, 30 Oct 2019 12:08:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iPqVu-0002al-0d for bug-gnu-emacs@gnu.org; Wed, 30 Oct 2019 12:08:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 30 Oct 2019 16:08:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25672 X-GNU-PR-Package: emacs Original-Received: via spool by 25672-submit@debbugs.gnu.org id=B25672.15724516379905 (code B ref 25672); Wed, 30 Oct 2019 16:08:01 +0000 Original-Received: (at 25672) by debbugs.gnu.org; 30 Oct 2019 16:07:17 +0000 Original-Received: from localhost ([127.0.0.1]:51311 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iPqVB-0002Zh-9u for submit@debbugs.gnu.org; Wed, 30 Oct 2019 12:07:17 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:59004) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iPqV9-0002ZY-8K for 25672@debbugs.gnu.org; Wed, 30 Oct 2019 12:07:15 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPqV5-0000Pk-Eu; Wed, 30 Oct 2019 17:07:13 +0100 In-Reply-To: ("=?UTF-8?Q?Cl=C3=A9ment?= Pit--Claudel"'s message of "Thu, 9 Feb 2017 16:22:21 -0500") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:170425 Archived-At: Cl=C3=A9ment Pit--Claudel writes: > Eli remarked the following: > >> However, please explain why font-lock-ensure-function calls >> font-lock-DEFAULT-fontify-buffer. If it's supposed to be good for >> any mode, why >> does it call the default fontification? >> >> As a matter of fact, if I replace the font-lock-default-fontify-buffer >> call with a call to font-lock-fontify-buffer, the problem described by >> the OP goes away. That is why I said what I said. > > And Stefan answered: > >> I haven't seen the beginning of the thread, but if that fixes the >> problem, then I think it's a good change. >> >> To go back to the previous question. I guess I used >> font-lock-default-fontify-buffer because the whole point is to get rid >> of all the misuses of font-lock-fontify-buffer, but I think in this case >> it's indeed the right thing to do. I think this was fixed last year-ish if I'm reading the change log correctly. Currently, font-lock-ensure calls the value of font-lock-ensure-function, which has a default value of (lambda (beg end) (unless font-lock-fontified (save-excursion (font-lock-fontify-region beg end)))) If global-font-lock-mode is on, it's jit-lock-fontify-now. So I think this now works better, and I'm closing this bug report. If this is still an issue, please reopen. --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no