From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: What to do when font-lock-flush + font-lock-ensure do less than font-lock-fontify-buffer? Date: Wed, 24 Feb 2016 15:09:26 -0500 Message-ID: References: <56CA94A8.3000205@gmail.com> <83bn76hw1o.fsf@gnu.org> <838u29hq9x.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1456344585 17794 80.91.229.3 (24 Feb 2016 20:09:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Feb 2016 20:09:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 24 21:09:36 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aYfke-0005Ju-1k for ged-emacs-devel@m.gmane.org; Wed, 24 Feb 2016 21:09:36 +0100 Original-Received: from localhost ([::1]:38086 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfkd-0008Jy-65 for ged-emacs-devel@m.gmane.org; Wed, 24 Feb 2016 15:09:35 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:32834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfkZ-0008Jl-HE for emacs-devel@gnu.org; Wed, 24 Feb 2016 15:09:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYfkV-0006G7-Dl for emacs-devel@gnu.org; Wed, 24 Feb 2016 15:09:31 -0500 Original-Received: from pruche.dit.umontreal.ca ([132.204.246.22]:47778) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfkV-0006Fy-8b; Wed, 24 Feb 2016 15:09:27 -0500 Original-Received: from fmsmemgm.homelinux.net (lechon.iro.umontreal.ca [132.204.27.242]) by pruche.DIT.UMontreal.CA (8.14.1/8.14.1) with ESMTP id u1OK9KtC029688; Wed, 24 Feb 2016 15:09:20 -0500 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 6A1A8AE22C; Wed, 24 Feb 2016 15:09:26 -0500 (EST) In-Reply-To: <838u29hq9x.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 24 Feb 2016 21:17:14 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV5591=0 X-NAI-Spam-Version: 2.3.0.9418 : core <5591> : inlines <4381> : streams <1592895> : uri <2150568> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200639 Archived-At: > However, please explain why font-lock-ensure-function calls > font-lock-DEFAULT-fontify-buffer. Good question. > 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. 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. Stefan