bug#66004: closed ([PATCH] Offset ranges before applying embeded treesit parsers)

[GNU bug Tracking System]

Your message dated Mon, 18 Sep 2023 15:52:43 -0700
with message-id 
<CADwFkmkA4b65KYHc-8feyXramv7jOt62ypQRe4+HSf64uUCbOQ@mail.gmail.com>
and subject line Re: bug#66004: [PATCH] Offset ranges before applying embeded 
treesit parsers
has caused the debbugs.gnu.org bug report #66004,
regarding [PATCH] Offset ranges before applying embeded treesit parsers
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
66004: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66004
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH] Offset ranges before applying embeded treesit parsers Date: Fri, 15 Sep 2023 11:45:00 -0400

Background: In clojure-ts-mode I've been capturing docstrings and
applying some limited syntax highlighting using an embedded markdown
parser. I'm only able to capture the full string, "quotes included". I
would like to be able to easily adjust the ranges captured to only
include the contents of the string, delimiters excluded. I have a
similar desire to capture the contents of a regular expression literal
and apply a nested regex grammar.

I've seen an offset mechanism used by the neovim tree-sitter integration
for similar purposes.

I believe the javascript/typescript modes could take advantage of this
with template strings. I've included a small test in the patch that
demonstrates this.

0001-Offset-ranges-before-applying-embedded-tree-sitter-p.patch
Description: Text Data

Let me know what you think.

Thank you,
-- 
Danny Freeman

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#66004: [PATCH] Offset ranges before applying embeded treesit parsers
>
>
>
>
> Date: 
>
> Mon, 18 Sep 2023 15:52:43 -0700
>
>
>
>
> Yuan Fu <casouri@gmail.com> writes:
>
> > I made some minor changes and pushed to master, thanks again!
>
> It seems like the patch was installed, but was left open in the bug
> tracker.  I'm therefore closing it now.
>
>
> --- End Message ---