From: Josh Berdine <josh@berdine.net>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
Yuan Fu <casouri@gmail.com>
Cc: 19080@debbugs.gnu.org
Subject: bug#19080: 24.4; wish: enable show-paren-mode to highlight matching same-level keywords
Date: Fri, 13 May 2022 12:48:25 +0100 [thread overview]
Message-ID: <8164837F-1011-4DF5-B875-0BA30317559A@berdine.net> (raw)
In-Reply-To: <83k0aqnfm5.fsf@gnu.org>
>> I think, that adding tree-sitter “backend” needs refactoring existing code non-trivially.
>
> If show-paren-mode would want to use tree-sitter, it will need
> refactoring, yes. Which other packages you envision could benefit
> from using tree-sitter?
For some context, this originally came up in discussion of
https://github.com/ocaml/tuareg/issues/26 and the related https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19079 . This issue is about incorrect highlighting due to an smie bug, which tuareg-mode uses. As far as I understand, the incorrect highlighting prevents implementing navigation functions e.g. from a `let` to the matching `in`. I expect that tree-sitter can have a better understanding of the actual code structure than smie, and so tuareg-mode would be a package that could benefit. There is an ocaml (the language tuareg-mode supports) grammar for tree-sitter. I don't have the expertise to volunteer to work on that though.
next prev parent reply other threads:[~2022-05-13 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:34 bug#19080: 24.4; wish: enable show-paren-mode to highlight matching same-level keywords Josh Berdine
2022-05-12 1:44 ` Lars Ingebrigtsen
2022-05-12 5:36 ` Eli Zaretskii
2022-05-12 22:52 ` Yuan Fu
2022-05-13 5:52 ` Eli Zaretskii
2022-05-13 11:48 ` Josh Berdine [this message]
2022-05-14 5:05 ` Yuan Fu
2022-05-14 8:00 ` Visuwesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8164837F-1011-4DF5-B875-0BA30317559A@berdine.net \
--to=josh@berdine.net \
--cc=19080@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).