From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Partly deferred font-locking? Date: Thu, 12 Jan 2023 16:30:41 +0200 Message-ID: <838ri7bzam.fsf@gnu.org> 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> <87r0vz96d6.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4816"; mail-complaints-to="usenet@ciao.gmane.io" Cc: michael_heerdegen@web.de, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 12 15:43:40 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 1pFynr-0000lM-Sf for ged-emacs-devel@m.gmane-mx.org; Thu, 12 Jan 2023 15:43:40 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pFybS-0001ku-H1; Thu, 12 Jan 2023 09:30:50 -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 1pFybQ-0001jc-5b for emacs-devel@gnu.org; Thu, 12 Jan 2023 09:30:48 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pFybP-0002Il-KA; Thu, 12 Jan 2023 09:30:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=OZOf9+jGOd7AUOElZvSKcUZ9h9M+NfiNOgMMf/raI9E=; b=ihvb5H+yUe75 BzjRuFyQgg+m5HQs2yuVn+43CHoprd6tFzXNOcMyLWF4eA/xf0FHUZg2qHWfjPpyIysoHqukAgzTi bLDPJLJRuJWSZbTU6atB8YQtKzLhhB53HAZ/QRzW56nsBKw1qgrJWJ8XGaOzuh1Jg7o50AN1XSscc WVlaFbmvVz+gHwaMY2GC58Yo7Awz74F7HNlq1qfLYU8vXAqA+ejgrirxkHV1nM4E4efmEuoaPbp9i hMp/7xQ3RM46ifMRF8EqvMV9uSGM7EnB7qOzsLULdRmtr68TFgFkzGDFr1hAuI/5EywZuVn/np+98 7mDwO64WDM1Cg3cBbXMBiQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pFybM-0002dF-SD; Thu, 12 Jan 2023 09:30:45 -0500 In-Reply-To: <87r0vz96d6.fsf@localhost> (message from Ihor Radchenko on Thu, 12 Jan 2023 14:26:13 +0000) 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:302377 Archived-At: > From: Ihor Radchenko > Cc: Michael Heerdegen , emacs-devel@gnu.org > Date: Thu, 12 Jan 2023 14:26:13 +0000 > > Eli Zaretskii writes: > > >> 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. > > > > 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. > > Yet, there is observable difference. > AFAIK, helm does use `while-no-input' and I've seen helm being > non-blocking on functions that are not designed with interrupts in mind. > I suspect that you are missing something. Maybe you are missing what I wrote about testing quit-flag? > More complex fontification may stumble on _editing_ long lines - if > fontification is performed line-by-line, long lines can slow down the > performance significantly (which is a known problem). It is often > a reasonable trade-off to defer re-fontification while editing a long > line and re-fontify it later. I have stumbled upon this issue myself in > my parser-based fontification for Org. It's a trade-off: you assume that users don't want to see the fontifications change in near real-time when editing long lines, but that is just an assumption, not necessarily true.