From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.devel Subject: Re: Partly deferred font-locking? Date: Thu, 12 Jan 2023 14:14:15 +0100 Message-ID: <87o7r3gajc.fsf@web.de> References: <87bkn52dso.fsf@web.de> <834jsxm0c7.fsf@gnu.org> <871qo03omi.fsf@web.de> <83zgaolu7o.fsf@gnu.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="6780"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:NfHs5t/XaPF+MDLqI7s9n3LmhLE= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 12 14:15:24 2023 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 1pFxQS-0001OJ-1r for ged-emacs-devel@m.gmane-mx.org; Thu, 12 Jan 2023 14:15:24 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pFxPY-0005M9-HQ; Thu, 12 Jan 2023 08:14:28 -0500 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 1pFxPW-0005Lk-OM for emacs-devel@gnu.org; Thu, 12 Jan 2023 08:14:27 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pFxPV-0003Fv-8J for emacs-devel@gnu.org; Thu, 12 Jan 2023 08:14:26 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pFxPQ-000AdB-JV for emacs-devel@gnu.org; Thu, 12 Jan 2023 14:14:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.067, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302371 Archived-At: Eli Zaretskii writes: > My point is that your example is the exception rather than the rule. > Fontifications almost never access files or do any other fancy stuff > like that. At least AFAIK. Yes yes, all good. But I missed a feature like this for several times. One application is syntax-based highlighting of el-search matches, for example. Or a hi-lock like thing but not restricted to simple regexps. I implemented the el-search hi-lock library more or less without font-lock, but were reinventing parts of it. Maybe there would be more use cases if Emacs would support this kind of highlighting, I don't know. If you wanted to add some more expensive on-the-fly highlighting, how would you do it? Currently, one can't use font-lock directly: when the additional deferred highlighting doesn't happen for a buffer chunk but normal font-locking was performed, the deferred highlighting would not be triggered again when that buffer area gets visible again. So I think I would have to remember which parts of the buffer where treated by the deferred highlighting by myself, I would have to keep that information in an additional variable. That feels a bit odd since this is one of the things that font-lock naturally does. I need to reinvent parts of font-lock. Michael.