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: Reliable after-change-functions (via: Using incremental parsing in Emacs) Date: Tue, 31 Mar 2020 18:44:57 +0300 Message-ID: <83imik1qbq.fsf@gnu.org> References: <83o8sf3r7i.fsf@gnu.org> <2E218879-0F24-4A20-B210-263C8D0BEEA4@gmail.com> <838sjh2red.fsf@gnu.org> <83369o3bvb.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="88309"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, akrl@sdf.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 31 17:45:40 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 1jJJ5A-000MrB-2A for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 17:45:40 +0200 Original-Received: from localhost ([::1]:40606 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJJ58-00087n-WF for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 11:45:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36932) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJJ4M-0006y0-P7 for emacs-devel@gnu.org; Tue, 31 Mar 2020 11:44:51 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41229) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJJ4M-000521-8M; Tue, 31 Mar 2020 11:44:50 -0400 Original-Received: from [176.228.60.248] (port=2533 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJJ4L-00011r-Ec; Tue, 31 Mar 2020 11:44:49 -0400 In-Reply-To: (message from Stefan Monnier on Tue, 31 Mar 2020 11:11:22 -0400) 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:246114 Archived-At: > From: Stefan Monnier > Cc: casouri@gmail.com, emacs-devel@gnu.org, akrl@sdf.org > Date: Tue, 31 Mar 2020 11:11:22 -0400 > > > I still don't see why it would need the entire buffer for this class > > of applications. Did anyone try the alternatives, in particular on > > very large buffers? > > What alternatives? Let tree-sitter see just a portion of the buffer, like the outer block of what will be displayed in the window. You are saying that this is impossible, but do tree-sitter developers also say that? > How large is "very large" here? xdisp.c comes to mind, obviously.