From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to add pseudo vector types Date: Sat, 24 Jul 2021 20:42:57 +0300 Message-ID: <83mtqby5em.fsf@gnu.org> References: <83h7gw6pyj.fsf@gnu.org> <45EBF16A-C953-42C7-97D1-3A2BFEF7DD01@gmail.com> <83y2a764oy.fsf@gnu.org> <83v95b60fn.fsf@gnu.org> <00DD5BFE-D14E-449A-9319-E7B725DEBFB3@gmail.com> <83r1fz5xr9.fsf@gnu.org> <1AAB1BCC-362B-4249-B785-4E0530E15C60@gmail.com> <83czri67h0.fsf@gnu.org> <46BBFF88-76C3-4818-8805-5437409BEA93@gmail.com> <83wnpq46uk.fsf@gnu.org> <533BD53B-4E85-4E9E-B46A-346A5BBAD0F5@gmail.com> <258CB68D-1CC1-42C8-BDCD-2A8A8099B783@gmail.com> <1a776770-50b7-93cd-6591-c9a5b3a56eb8@gmail.com> <8335s64v10.fsf@gnu.org> <5380C92B-6C15-4490-A1E0-1C3132DBB16A@gmail.com> <83k0li2shw.fsf@gnu.org> <83eebq2mpy.fsf@gnu.org> <83lf5w26e3.fsf@gnu.org> <834kcjzo2y.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26450"; mail-complaints-to="usenet@ciao.gmane.io" Cc: cpitclaudel@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 24 19:44:11 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 1m7Lh4-0006l7-QZ for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 19:44:10 +0200 Original-Received: from localhost ([::1]:53364 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7Lh3-0003zy-Sj for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 13:44:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38522) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Lg6-0003Ih-Id for emacs-devel@gnu.org; Sat, 24 Jul 2021 13:43:11 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46646) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7Lg6-0007ek-Aq; Sat, 24 Jul 2021 13:43:10 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1091 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7Lg5-00072a-T2; Sat, 24 Jul 2021 13:43:10 -0400 In-Reply-To: (message from Yuan Fu on Sat, 24 Jul 2021 13:32:18 -0400) 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:271567 Archived-At: > From: Yuan Fu > Date: Sat, 24 Jul 2021 13:32:18 -0400 > Cc: monnier@iro.umontreal.ca, > cpitclaudel@gmail.com, > emacs-devel@gnu.org > > >> +(define-derived-mode ts-c-mode prog-mode "TS C" > >> + "C mode with tree-sitter support." > >> + (setq-local font-lock-fontify-region-function > >> + #'tree-sitter-fontify-region-function) > >> + (setq-local tree-sitter-font-lock-settings > >> + `(("font-lock-c" > >> + ,(tree-sitter-c) > >> + "(null) @font-lock-constant-face > >> +(true) @font-lock-constant-face > >> +(false) @font-lock-constant-face > >> + > >> +(comment) @font-lock-comment-face > >> + > >> +(system_lib_string) @ts-c-fontify-system-lib > >> + > >> +(unary_expression > >> + operator: _ @font-lock-negation-char-face) > >> + > >> +(string_literal) @font-lock-string-face > >> +(char_literal) @font-lock-string-face > > > > Where does this repertoire of possible syntax categories come from? > > Is this from some list that TS exposes or documents? If so, what > > happens when the repertoire is modified? > > These “syntax categories” are defined by individual language grammar definition for tree-sitter, so it could change from language to language. And tree-sitter does not document them. If these “syntax categories” change, then we need to change our code with them. But I doubt that it will happen often. They are hard to document, because a non-trivial grammar definition often defines hundreds of them; the grammar definition for C has 1000 LOC. Isn't there a better way of updating those than manually take them out of the TS grammar? Maybe write a short program linked against TS that would spill them in some format that's convenient to use? Manual updates are a serious maintenance burden.