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: Wed, 01 Apr 2020 05:23:38 +0300 Message-ID: <83sghoymdx.fsf@gnu.org> References: <83o8sf3r7i.fsf@gnu.org> <2E218879-0F24-4A20-B210-263C8D0BEEA4@gmail.com> <838sjh2red.fsf@gnu.org> <83369o3bvb.fsf@gnu.org> <816186eb-baac-f5c7-04df-a3f30780d91d@yandex.ru> <83k1301qq4.fsf@gnu.org> <834ku41km9.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="46503"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, akrl@sdf.org, emacs-devel@gnu.org, dgutov@yandex.ru To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 01 04:24:05 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 1jJT2y-000C0D-Ls for ged-emacs-devel@m.gmane-mx.org; Wed, 01 Apr 2020 04:24:04 +0200 Original-Received: from localhost ([::1]:46124 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJT2x-0001bA-KT for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 22:24:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58828) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJT2M-0000z2-EL for emacs-devel@gnu.org; Tue, 31 Mar 2020 22:23:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54162) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJT2L-00008y-6n; Tue, 31 Mar 2020 22:23:25 -0400 Original-Received: from [176.228.60.248] (port=1673 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJT2K-00067S-HY; Tue, 31 Mar 2020 22:23:25 -0400 In-Reply-To: (message from Stefan Monnier on Tue, 31 Mar 2020 15:35:41 -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:246177 Archived-At: > From: Stefan Monnier > Cc: dgutov@yandex.ru, casouri@gmail.com, akrl@sdf.org, emacs-devel@gnu.org > Date: Tue, 31 Mar 2020 15:35:41 -0400 > > You basically always need to en/decode the content (even if it is into > utf-8, we still need to handle the potential raw-bytes), so a copy is > hard to avoid. It isn't hard in this case, AFAICT. Tree-sitter has an API where we can provide a function that will deliver text at a given offset. We should use that to access buffer text directly. We can avoid encoding the buffer text by converting raw bytes into something like U+FFFD, or something else that tree-sitter will ignore.