> On Nov 15, 2022, at 10:27 AM, Visuwesh <visuweshm@gmail.com> wrote: > > [à®à¯à®µà¯à®µà®¾à®¯à¯ நவமà¯à®ªà®°à¯ 15, 2022] Eli Zaretskii wrote: > >>> From: Stefan Monnier <monnier@iro.umontreal.ca> >>> Cc: Yuan Fu <casouri@gmail.com>, theo@thornhill.no, emacs-devel@gnu.org >>> Date: Tue, 15 Nov 2022 11:01:24 -0500 >>> >>>> I guess we need to report these to the developers of the Tree-sitter's >>>> C parser? Is there anything else we could do until they fix >>>> the parser? >>> >>> AFAIK the tree-sitter parser parses basically already-preprocessed C. >>> It's wickedly hard to parse meaningfully notyet-preprocessed C with >>> something based on a BNF grammar. >> >> There are a lot of macros in our code that tree-sitter based C mode >> gets right, so I'm not sure this is accurate. >> >>> So my guess is that this is going to be a "wont fix". >> >> Maybe we should grow some augmentations for tree-sitter, at least >> given enough time. Or maybe it's possible to identify the parts where >> this happens by some tree-sitter indications, and tweak the faces in >> those regions in some way. > > I'm not sure how similar the emacs-tree-sitter > (https://github.com/ubolonton/emacs-tree-sitter) and Yuan's code are but > in his EmacsConf 2020 talk, Tuấn-Anh Nguyá» n wrote some custom > tree-sitter query (?) to correctly parse our macros and highlighted the > type, the function name, etc. with the approriate faces. > You can find his talk here: https://emacsconf.org/2020/talks/23 and his > demonstration of the Emacs source code is around the 20 minute mark > (after a quick search in the subtitles). Oh nice, Iâll check that out. CCing him for some insights :-) Yuan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4