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 15:00:43 +0100 Message-ID: <87ilhbg8dw.fsf@web.de> References: <87bkn52dso.fsf@web.de> <834jsxm0c7.fsf@gnu.org> <871qo03omi.fsf@web.de> <83zgaolu7o.fsf@gnu.org> <87o7r3gajc.fsf@web.de> <83cz7jc1d6.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="14467"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:z7PHhMho8WjHe2itlNlm7kjq0V4= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 12 15:03:25 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 1pFyAt-000364-Mr for ged-emacs-devel@m.gmane-mx.org; Thu, 12 Jan 2023 15:03:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pFy8W-0000cT-PG; Thu, 12 Jan 2023 09:00:56 -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 1pFy8V-0000bw-B3 for emacs-devel@gnu.org; Thu, 12 Jan 2023 09:00:55 -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 1pFy8T-0005fx-HL for emacs-devel@gnu.org; Thu, 12 Jan 2023 09:00:54 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pFy8R-000AUE-RW for emacs-devel@gnu.org; Thu, 12 Jan 2023 15:00:51 +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:302373 Archived-At: Eli Zaretskii writes: > Both jit-lock-defer-time and jit-lock-stealth-time defer highlighting > to when enough idle time has passed since last command. Is that what > you want -- to be able to complement the highlighting by more > highlighting? Exactly that. > If so, you'd need to change the 'fontified' property to > have more than just a boolean value, and you'd need a special timer > which examined the 'fontified' property and applied more highlighting > if the value says it wasn't applied yet. That would have to be done in Emacs, not in my code, right? > Please note that expensive highlighting might make Emacs less > responsive. So far I'm always using `while-no-input' and code that doesn't cause trouble when it gets interrupted. With that approach I had been able to avoid this issue nearly completely. Michael.