From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#71345: Feature: unleash font-lock's secret weapon; handle Qfontified = non-nil Date: Wed, 05 Jun 2024 12:59:08 -0400 Message-ID: References: <8A929E16-AF10-4D2B-AD71-AEAD4435F016@gmail.com> <1F2B8726-7594-494F-AB9D-08C48B7BCC43@gmail.com> <798B70AF-69BD-479E-992E-5CE9B4924820@gmail.com> <86o78fk4ye.fsf@gnu.org> <865xunjqfb.fsf@gnu.org> Reply-To: Stefan Monnier Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30793"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 71345@debbugs.gnu.org, jdtsmith@gmail.com, dmitry@gutov.dev To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 05 19:37:59 2024 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 1sEuaF-0007jI-6D for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 05 Jun 2024 19:37:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sEua6-0000Jn-H6; Wed, 05 Jun 2024 13:37:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sEua4-0000Cb-D2 for bug-gnu-emacs@gnu.org; Wed, 05 Jun 2024 13:37:48 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sEua4-0007fa-3T for bug-gnu-emacs@gnu.org; Wed, 05 Jun 2024 13:37:48 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sEuaI-0006we-62 for bug-gnu-emacs@gnu.org; Wed, 05 Jun 2024 13:38:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 05 Jun 2024 17:38:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71345 X-GNU-PR-Package: emacs Original-Received: via spool by 71345-submit@debbugs.gnu.org id=B71345.171760902426549 (code B ref 71345); Wed, 05 Jun 2024 17:38:02 +0000 Original-Received: (at 71345) by debbugs.gnu.org; 5 Jun 2024 17:37:04 +0000 Original-Received: from localhost ([127.0.0.1]:51763 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sEuZL-0006u7-GP for submit@debbugs.gnu.org; Wed, 05 Jun 2024 13:37:03 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:22741) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sEuZI-0006tA-WA for 71345@debbugs.gnu.org; Wed, 05 Jun 2024 13:37:01 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 94DEA100043; Wed, 5 Jun 2024 12:59:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1717606748; bh=MW7ooe0rgxvB5yaiQV33WERms3LwAiEooEssVY2fCwk=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=cxvmQOEsKvRiSxtNWcj41zbCIzgd3RRcjEhmOdzfLgBGYTiu0wsFksAtyS7JZ3mT/ 4WV3xHXh5iHRIT7w/3tv3bXWbxdJiZP8spatdaFzs2t8uaTkHwMwkFtgHw7l/MQqST 1rM9XblHn1sCHXW9c+/N845TQrY7p0J4ekyvL4LhWWHHy1jqOaJj4M5tSjW8T8f84p ScoTsHuIVPZK4XiY4+H6QVoSgqH2ISUGq9lL0jfujC+XMfte0XSREQU0zkYwM9jGNB 6ksya0PTYNTEEEsHIlDk7OfWfSFLZT9P9kMiVAyjRjddtCL+lLavAG1sbQ/lxX1U9G bf/R9lCKztK+A== Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 9DDE010002E; Wed, 5 Jun 2024 12:59:08 -0400 (EDT) Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 87E601204F3; Wed, 5 Jun 2024 12:59:08 -0400 (EDT) In-Reply-To: <865xunjqfb.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Jun 2024 19:38:16 +0300") 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:286627 Archived-At: >> >> Because a given buffer can have several (window-)points, >> >> position-dependent highlighting will ideally want to be added via >> >> (window-specific) overlays rather than text-properties. >> > >> > Not sure I understand how this remark is relevant to the issue >> > discussed here, but let me just point out that when redisplay starts >> > working on a window, it temporarily moves point to the window-point >> > position. So position-dependent highlighting will behave in each >> > window according to its window-point, which I think is what's expected >> > here? >> >> But the highlighting is done "once and for all" (at least until the next >> command), so if you want it to be different in different windows (to >> reflect the different values of `point` in those windows) you'll need >> overlays with the `window` property because the highlighting will not be >> re-done in the middle of redisplay when we go from one window to another. > > In that case, we are in trouble anyway, because the "once and for all" > highlighting could be (by sheer luck) be done by display code that > doesn't run as part of redisplay, but as part of something else, like > vertical-motion. I can't see why that would be a problem. The highlighting code run from `jit-lock` will usually not be able to use `point` (or `window-point`) directly. Instead, that highlighter will need to keep track of the windows' points elsewhere "manually" via hooks like `post-command-hook` or `pre-redisplay-functions` and then rely on that info when performing the highlighting. Stefan