From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: What's the best (i.e. least bad) way to re-redisplay? Date: Wed, 25 Aug 2021 20:09:24 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30712"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 25 22:11:06 2021 Return-path: Envelope-to: ged-emacs-devel@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 1mIzEn-0007qv-R2 for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Aug 2021 22:11:05 +0200 Original-Received: from localhost ([::1]:40118 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mIzEl-0000fI-0x for ged-emacs-devel@m.gmane-mx.org; Wed, 25 Aug 2021 16:11:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52400) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mIzDS-0007rh-GX for emacs-devel@gnu.org; Wed, 25 Aug 2021 16:09:44 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:53674 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1mIzDQ-0001fB-6l for emacs-devel@gnu.org; Wed, 25 Aug 2021 16:09:42 -0400 Original-Received: (qmail 98032 invoked by uid 3782); 25 Aug 2021 20:09:25 -0000 Original-Received: from acm.muc.de (p4fe159e2.dip0.t-ipconnect.de [79.225.89.226]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Wed, 25 Aug 2021 22:09:25 +0200 Original-Received: (qmail 19772 invoked by uid 1000); 25 Aug 2021 20:09:24 -0000 Content-Disposition: inline In-Reply-To: X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:272990 Archived-At: Hello, Stefan. On Tue, Aug 24, 2021 at 18:43:04 -0400, Stefan Monnier wrote: > > The problem is, there will be occurences in the foreground window before > > the one which triggered the fontification. Redisplay will already have > > passed this earlier buffer position. So I need to trigger another > > redisplay immediately after the current one. > > What is the least bad way of doing this? > I think something along the lines of > (run-with-timer 0 nil > (lambda (buf) > (with-current-buffer buf (font-lock-flush))) > (current-buffer)) > is the cleanest that comes to mind. Thanks. That's probably cleaner than a direct use of jit-lock-force-redisplay. I'll just need to add BEG and END into that, somehow, but font-lock-flush has these as &optional parameters, so that won't be a problem. But, looking at the code, font-lock-flush works by clearing the 'fontified property, nothing more. This won't always trigger a redisplay, will it? Doesn't it need after-change-functions to be active at the time? Maybe after-change-functions will always be active during a redisplay (and hence immediately after redisplay completes), but my head's beginning to hurt. > Stefan -- Alan Mackenzie (Nuremberg, Germany).