From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-tree-sitter and Emacs Date: Wed, 01 Apr 2020 16:20:24 +0300 Message-ID: <83lfnfz6jr.fsf@gnu.org> References: <83eeta3sa0.fsf@gnu.org> <86369ojbig.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="70368"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 01 15:20:47 2020 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 1jJdIV-000IDm-8t for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 15:20:47 +0200 Original-Received: from localhost ([::1]:60260 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJdIU-0006ly-Bo for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 09:20:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36901) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJdHw-0006Kf-In for emacs-devel@gnu.org; Wed, 01 Apr 2020 09:20:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJdHv-0003Tq-RC; Wed, 01 Apr 2020 09:20:11 -0400 Original-Received: from [176.228.60.248] (port=1866 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJdHu-0004FI-BP; Wed, 01 Apr 2020 09:20:11 -0400 In-Reply-To: <86369ojbig.fsf@stephe-leake.org> (message from Stephen Leake on Tue, 31 Mar 2020 16:27:35 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:246187 Archived-At: > From: Stephen Leake > Date: Tue, 31 Mar 2020 16:27:35 -0800 > > > OTOH, using an after-change hook has its downsides, even if disregard > > slow-down (which I wouldn't). > > In wisi (used by ada-mode), the after-change hooks just record what > regions have been changed; font-lock then triggers a parse if the region > being fontified contains or is after a change region. Navigation and > indent also trigger parses. Can you tell in more detail why you need to rely on these hooks? They shouldn't be necessary, AFAIU. And they cannot pick up every relevant change; for example, what happens if some face used for font-lock is modified? > By default font-lock runs after every character typed No, it only runs when redisplay kicks in. If you type very quickly, it won't run for every character. At least AFAIR. > which is often too slow in an ada-mode buffer; I always set > jit-lock-defer-time to 1.0 seconds. That's too long to be pleasant on display, IMO. A second is a very long time in this context.