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: [SPAM UNSURE] Re: Reliable after-change-functions (via: Using incremental parsing in Emacs) Date: Fri, 03 Apr 2020 15:44:06 +0300 Message-ID: <83eet4wxgp.fsf@gnu.org> References: <83369o1khx.fsf@gnu.org> <83imijz68s.fsf@gnu.org> <831rp7ypam.fsf@gnu.org> <86wo6yhj4d.fsf@stephe-leake.org> <83o8sax803.fsf@gnu.org> <86pncpffmk.fsf@stephe-leake.org> <83v9mgx2a1.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="71269"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 03 14:45:06 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 1jKLh4-000IQc-8M for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Apr 2020 14:45:06 +0200 Original-Received: from localhost ([::1]:54846 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jKLh3-0007wO-9A for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Apr 2020 08:45:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54969) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jKLgJ-00075Q-Um for emacs-devel@gnu.org; Fri, 03 Apr 2020 08:44:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47278) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jKLgJ-0006dk-5y; Fri, 03 Apr 2020 08:44:19 -0400 Original-Received: from [176.228.60.248] (port=4264 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jKLgI-0008SV-Mk; Fri, 03 Apr 2020 08:44:19 -0400 In-Reply-To: (message from Robert Pluim on Fri, 03 Apr 2020 13:09:34 +0200) 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:246320 Archived-At: > From: Robert Pluim > Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org > Date: Fri, 03 Apr 2020 13:09:34 +0200 > > Eli> Not only raw bytes: also some characters that cannot be unified with > Eli> Unicode. > > And again: how likely are those characters to be in source code? Probably not too likely, but we need to have a solution for when they do happen. I guess a useful first step would be for someone to find out what does tree-sitter do when it encounters such byte sequences. We can then devise a solution that will produce good results, preferably without the need to ask tree-sitter developers to cater to these situations.