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:33:03 +0100 Message-ID: <87cz7jg6w0.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> <87ilhbg8dw.fsf@web.de> <83a62nc03x.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="10189"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) To: emacs-devel@gnu.org Cancel-Lock: sha1:tH3CYkEYPtixp7j6slnUc0yXnH0= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 12 16:13:56 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 1pFzH9-0002Er-Ok for ged-emacs-devel@m.gmane-mx.org; Thu, 12 Jan 2023 16:13:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pFye5-00034F-UW; Thu, 12 Jan 2023 09:33:34 -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 1pFydn-0002uf-F3 for emacs-devel@gnu.org; Thu, 12 Jan 2023 09:33:21 -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 1pFydl-0002Uu-PD for emacs-devel@gnu.org; Thu, 12 Jan 2023 09:33:15 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1pFydj-00061i-Nq for emacs-devel@gnu.org; Thu, 12 Jan 2023 15:33:11 +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:302382 Archived-At: Eli Zaretskii writes: > > That would have to be done in Emacs, not in my code, right? > > Depends on whether the additional highlighting will be part of > jit-lock.el or not. The display engine only cares whether the value > of 'fontified' is nil or not. I can't image a solution that is not part of jit-lock. > while-no-input is not a way to interrupt an on-going calculation, > because it requires Emacs to check whether any input arrived, and > Emacs only does that when it's idle. Only when idle? Why is (while-no-input (while t (+ 1 1))) interruptable? I don't think Emacs is idle while evaluating the loop...? > You are specifically talking about accessing the filesystem, which > means you will call some file I/O C API, and those won't be > interrupted. Right, but there are dozens of them per window size, and I think we can interrupt the thing between the individual request. Michael.