From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: font-lock-fontify-block Date: Thu, 11 Mar 2021 14:45:23 -0500 Message-ID: References: <87a6sbg41o.fsf@gnus.org> <87lfatirk1.fsf@gnus.org> <83blbpmy2x.fsf@gnu.org> <837dmdmw60.fsf@gnu.org> <30f0a4188eac8da31543@heytings.org> <30f0a4188e796ef64509@heytings.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="27003"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Mar 11 20:50:12 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 1lKRJz-0006t1-43 for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Mar 2021 20:50:11 +0100 Original-Received: from localhost ([::1]:56912 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lKRJy-0007aS-42 for ged-emacs-devel@m.gmane-mx.org; Thu, 11 Mar 2021 14:50:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49748) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lKRFV-0004QN-S4 for emacs-devel@gnu.org; Thu, 11 Mar 2021 14:45:33 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:49374) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lKRFQ-0005Ha-PR for emacs-devel@gnu.org; Thu, 11 Mar 2021 14:45:32 -0500 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 45FD644097E; Thu, 11 Mar 2021 14:45:27 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C3F86440BE1; Thu, 11 Mar 2021 14:45:25 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1615491925; bh=GTYO2HXCzIjhCeX+96NqzSudFQ+zDLCY1+XtTsZTcps=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=pTxe77K8lfp+BiTwI9+H21LrLWS7QucFIbB01/d7lQBjd4vDtYa+vq3wEFWvW4nKZ ke0TBbRoa9bdqt99IX4otKSdRg6NWlbApu/t+MEtVyqktqKnYjnuY3KLvOFatXJSJl Q6ujuE99rFTH0rUrmqC1VB4uYNcd3daY8QpMW2HY8jUHx3iy3cHSrdxXk/zKvH+PIw IA5F4gWDYqbSLSk5SE7+53jvxFtt2Wr1TA5RPeG+sAu3NSx68BkmP4r2IxbuMGetXn oNY1QvvrN2JsHUaGdHwTTiCGUMjqK/51pWswBgmwMXTj7zBENSRYu2gIg49S1lWizl Yly51xLJWkY4g== Original-Received: from alfajor (unknown [216.154.43.249]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id A82C8120310; Thu, 11 Mar 2021 14:45:25 -0500 (EST) In-Reply-To: <30f0a4188e796ef64509@heytings.org> (Gregory Heytings's message of "Thu, 11 Mar 2021 19:25:44 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:266356 Archived-At: >>>> Also, I suspect that for your use case, we could have a general >>>> "refresh" command, which just calls `font-lock-flush`, which would not >>>> depend on the ill-defined notion of "block" (and wouldn't mess with the >>>> mark). >>> >>> Yes, I agree that a >>> >>> (defun font-lock-fontify-window () >>> (interactive) >>> (font-lock-flush (window-start) (window-end))) >>> >>> would probably be useful. >> >> It could even flush from point-min to point-max. >> > > Is that not what font-lock-fontify-buffer already does (except during > narrowing)? Indeed (but that one, just like `font-lock-fontify-block`) suffers from a heavy heritage so it's messy and misused, so I'd be very happy to obsolete it (by replacing it with something simpler and that only caters to the relevant cases). Stefan