> On Nov 22, 2022, at 11:52 AM, Wilhelm Hugo Kirschbaum <wilhelm@floatpays.co.za> wrote:
> 
> On Tuesday, 22 November 2022 21:28:48 SAST Yuan Fu wrote:
>>> On Nov 22, 2022, at 9:24 AM, Wilhelm <wkirschbaum@gmail.com> wrote:
>>> 
>>> Is there perhaps an example using treesit-range-rules? To following
>>> attempt to set treesit-range-settings does not seem to have the desired
>>> effect.
>>> 
>>> (defvar heex--treesit-range-rules
>>> 
>>> (treesit-range-rules
>>> 
>>>  :embed 'elixir
>>>  :host 'heex
>>> 
>>>  '((directive (partial_expression_value) @cap)
>>> 
>>>    (directive (expression_value) @cap)
>>>    (expression (expression_value) @cap))))
>>> 
>>> (setq-local treesit-range-settings heex--treesit-range-rules)
>>> 
>>> The following error also pops up when modifying the buffer when removing
>>> buffer content:
>>> 
>>> Error during redisplay: (jit-lock-function 1) signaled
>>> (treesit-range-invalid "RANGE is either overlapping, out-of-order or
>>> out-of-range" ((11 . 20)))
>>> 
>>> The full attempt is here:
>>> https://github.com/wkirschbaum/elixir-mode/blob/main/heex-mode.el
>> Thanks Wilhelm. It would be nice if you can provide some example source file
>> of heex for me to experiment with. I tried to find some on the internet but
>> didn’t get very far :-)
>> 
>> Yuan
> 
> Thanks for having a look as I was not sure if this was meant to be used yet. 
> 
> A heex file can be as simple as this: 
> 
> #sample.html.heex
> <div>
>  <%= Enum.map([1, 2], &(&1 + 1)) %>
> </div>
> 
> and the directive <%= (partial_expression_value) %> should then be elixir., 
> not heex.
> 
> When checking with (treesit-language-at (point))  for the embed it still show.
> 
> Wilhelm

Cool. Please see if this works. Admittedly the process is a little “raw”. That’s mainly due to me not wanting to commit to a framework before we have a lot of real-world experience with multi-language major modes. Please let me know if you think how could this be improved. For starters, maybe someways to “inherit” font-lock rules with treesit-font-lock-rules? Maybe the feature-list should have independent configuration for each language, so we don’t have feature-namespace conflicts? (Right now we rename all elixir features to elixir-<feature>.)

I’ve also fixed the warning you see (which is due to treesit.el, not your code), so you’ll need to pull master.

Thanks!
Yuan