From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: cc-mode fontification feels random Date: Fri, 04 Jun 2021 14:25:23 -0400 Message-ID: References: <831r9iw473.fsf@gnu.org> <2d6d1cb0-2e8f-ceea-cb83-3bb840b65115@dancol.org> <83zgw6udxt.fsf@gnu.org> <87czt1zzns.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39237"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Eli Zaretskii , Daniel Colascione , emacs-devel@gnu.org To: =?windows-1252?B?Sm/jbyBU4XZvcmE=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jun 04 20:28:30 2021 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 1lpEYY-0009rD-0F for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Jun 2021 20:28:30 +0200 Original-Received: from localhost ([::1]:58496 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lpEYW-0001AC-U3 for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Jun 2021 14:28:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43260) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lpEVh-0002kR-QW for emacs-devel@gnu.org; Fri, 04 Jun 2021 14:25:33 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:40326) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lpEVe-0002Fz-KQ; Fri, 04 Jun 2021 14:25:32 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4631710031F; Fri, 4 Jun 2021 14:25:26 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id A2EC81002E9; Fri, 4 Jun 2021 14:25:24 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1622831124; bh=jYoEku9WgReKYKcbPlkUdYueXwZJ6MiN7wpcMN24vtE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=eDEj1xC7qURe0Hb7zjh10SjoJONuO/vQyZ4DVZVtZQ9u3LqseDpVG5EpaFvQ/nXbF uct3jvYCtRJiWS0uJZXWoXDCVGmJ4wDhtGE3IPaZTi/GHknEdN3srVtXxrhcdd4578 k5PRGfGPIukxqB8Q8EG9aR8cDeNMjEqarR8Sh0crbJ9aRD6MgPahPrvh2X9VLf/tNs 8EEDW5S1FaXfWC2YuPfQqSEdO0EucFMDY5hdJUroW4YbeFnNXpxdvZ48mTsKlq69A3 yfUGZB9UIPfykm/md6ctFuFzB6rVXHkmOIWFa0AZAn2TpxLoRFmytqDGDdVs8s2221 3s7iXHsHyC7eQ== Original-Received: from alfajor (69-196-163-239.dsl.teksavvy.com [69.196.163.239]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 612D112001E; Fri, 4 Jun 2021 14:25:24 -0400 (EDT) In-Reply-To: <87czt1zzns.fsf@gmail.com> (=?windows-1252?Q?=22Jo=E3o_T=E1vo?= =?windows-1252?Q?ra=22's?= message of "Fri, 04 Jun 2021 11:34:31 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:270395 Archived-At: > But I don't understand what's stopping these tree-sitter C modules (like > [1] and [2]) to have access to the buffer's contents directly and have > the best of both worlds. I think it's a direct result of them being "modules": the API doesn't let modules access a buffer's content directly, so it's more efficient copy the content via `buffer-substring` and toss it on the other side than having to use something like `char-after`. Stefan