Show-set rules lose highlighting with `where` specifications

[thornoar]

Consider the following show-set rule:

#show heading.where(level: 2): set text(stroke: red)

Here, the text becomes white after the second colon. In fact, it seems that the problem is the symbols between the first colon and the set keyword. If these symbols exist, the highlighting is lost. However, such show-set rules start being correctly highlighted if the unnamed function notation (=>) is used, like that:

#show heading.where(level: 2): it => {
  // something
}

Unfortunately, this does not seem to be a reliable workaround. In some cases, a show-set rule (like the first one) is necessary, for example when you need to modify the behavior of the very function you select for.

[kaarmu]

Sorry for the slow response! It looks like the show statement ends early at the first colon. I am fairly certain about why that happens, though I need to think a bit how to resolve that in a good way. Thank you for reporting this!

[kaarmu]

Some progress being made on branch fix-100...

Problem remaining: typstCodeRestOfLine doesn't end on the first $. So, below foo will match as code.

#show heading.where(level: 2): set text(stroke: red)  
foo
bar