From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel Subject: Re: emacs-tree-sitter and Emacs Date: Thu, 02 Apr 2020 12:19:44 -0400 Message-ID: References: <83eeta3sa0.fsf@gnu.org> <86369ojbig.fsf@stephe-leake.org> <83lfnfz6jr.fsf@gnu.org> <864ku3htmb.fsf@stephe-leake.org> <83v9mix9vk.fsf@gnu.org> <87pncq55f8.fsf@md5i.com> <83imihyl42.fsf@gnu.org> <83h7y1yikx.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="37461"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: mwd@md5i.com, stephen_leake@stephe-leake.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 02 18:20:53 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 1jK2aK-0009bZ-5P for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Apr 2020 18:20:52 +0200 Original-Received: from localhost ([::1]:44326 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jK2aJ-0004Zl-7C for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Apr 2020 12:20:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34843) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jK2ZL-0003vh-N4 for emacs-devel@gnu.org; Thu, 02 Apr 2020 12:19:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jK2ZK-0008By-HI for emacs-devel@gnu.org; Thu, 02 Apr 2020 12:19:51 -0400 Original-Received: from veto.sei.cmu.edu ([147.72.252.17]:47538) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jK2ZI-0007mk-7b; Thu, 02 Apr 2020 12:19:48 -0400 Original-Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 032GJkra011145; Thu, 2 Apr 2020 12:19:46 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu 032GJkra011145 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1585844386; bh=cmZoknNTSeSWZXYjkhGqLqsrTUgW9vwu5ywHOLhks4E=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=HoAia8SAxP2NCBdobnvRkngKB7NEeRi3Wk0vL242m70gJs0E6jR5Z7bB1I394EKju AlDP5dvidFMftuyCvkFV5+4G2on27r81WAD7KqTPw58oRXN8IfbjFkt7xk5piMn2Vl XfCs6PGkeKCz9CtV1iU8B8wvD3r4bNCDqdyXJBeU= Original-Received: from lx-birch.ad.sei.cmu.edu (lx-birch.ad.sei.cmu.edu [10.64.53.120]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 032GJj6L013651; Thu, 2 Apr 2020 12:19:45 -0400 Original-Received: from lx-birch.ad.sei.cmu.edu (localhost [127.0.0.1]) by lx-birch.ad.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 032GJiZP024228; Thu, 2 Apr 2020 12:19:44 -0400 Original-Received: (from mwd@localhost) by lx-birch.ad.sei.cmu.edu (8.14.7/8.14.7) id 032GJiZg024225; Thu, 2 Apr 2020 12:19:44 -0400 X-Authentication-Warning: lx-birch.ad.sei.cmu.edu: mwd set sender to mwd@cert.org using -f In-Reply-To: <83h7y1yikx.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 2 Apr 2020 19:10:22 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 147.72.252.17 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:246274 Archived-At: Eli Zaretskii writes: >> From: Michael Welsh Duggan >> Cc: Michael Welsh Duggan , , >> >> Date: Thu, 02 Apr 2020 11:24:33 -0400 >> >> Eli Zaretskii writes: >> >> > Each buffer always knows which part of it remains unchanged. When >> > fontification is invoked, it should start from that place. So there's >> > no need to parse _all_ prior context. >> >> Why not? Won't it miss that hypothetical opening comment delimiter, for >> example? > > No, because that was already taken care of when that comment delimiter > was inserted. In which case it's covered by the paragraph you omitted. -- Michael Welsh Duggan (mwd@cert.org)