Modifying text around an inline code block in vim mode breaks highlighting

[Ratainen]

• The Plugin is up to date
• Obsidian is up to date

Describe the bug
When modifying text around an inline code block in vim mode, the highlighting will sometimes break until you restart. You will also get this error in the dev console:

app.js:1 RangeError: Position 25 is out of range for changeset of length 23
at e.mapPos (app.js:1:274503)
at e.map (app.js:1:304757)
at e.map (app.js:1:306904)
at ii.ViewPlugin.fromClass.decorations.update (plugin:shiki-highlighter:279:1355)
at e.update (app.js:1:363559)
at e.updatePlugins (app.js:1:472715)
at e.update (app.js:1:470762)
at e.dispatchTransactions (app.js:1:467223)
at e.dispatch (app.js:1:469370)
at mB (app.js:1:1652494)

To Reproduce

1. Enable vim mode

2. Paste this into a note:
   aaa
   {rust} let abc = 123;

3. Delete the "aaa" line with dd

4. Make a new line with o

5. See the highlighting disappear and an error in the console

Expected behavior
There shouldn't be any errors and the highlighting would stay.

Screenshots

Occurs on

• Windows
• macOS
• Linux
• Android
• iOS

Plugin version
0.7.0

Additional context
I disabled all other plugins to test this, the only other non vanilla thing here is the theme.

[Seagull2004]

I've notice quite the opposite. When is go around my notes with vim motion sometimes the coloration goes completly random like this screenshot:

(yes i'm italian 🇮🇹)

I've tried to fix this behavior with the use of this snippet:

span.cm-header-1:not(.HyperMD-codeblock) > span[style*="color"],
span.cm-header-2:not(.HyperMD-codeblock) > span[style*="color"],
span.cm-header-3:not(.HyperMD-codeblock) > span[style*="color"],
span.cm-header-4:not(.HyperMD-codeblock) > span[style*="color"],
span.cm-header-5:not(.HyperMD-codeblock) > span[style*="color"],
span.cm-header-6:not(.HyperMD-codeblock) > span[style*="color"],
span:not(.cm-inline-code) > span[style*="color"],
div:not(.HyperMD-codeblock) > span[style*="color"] {
  color: unset !important;
}

what it does it to "unset" the coloration that shiki put in the elements of the notes but only if the element with that coloration is note some code.

The result is the correct coloration:

(i'm on macos btw)

[Seagull2004]

As you can see i can't replicate what you say:

[Ratainen]

@Seagull2004 Hmm, the bug does not seem to happen if there are enough (the number seems to be inconsistent) lines after the line you delete. What if you just try making an empty note and doing that delete and new line thing?

[Seagull2004]

Yes you are right, if I try to do the trick whit a brand new file i get the error

app.js:1 RangeError: Position 21 is out of range for changeset of length 20
    at t.mapPos (app.js:1:274503)
    at e.map (app.js:1:304785)
    at e.map (app.js:1:306904)
    at ii.ViewPlugin.fromClass.decorations.update (plugin:shiki-highlighter:279:1355)
    at e.update (app.js:1:363559)
    at e.updatePlugins (app.js:1:472715)
    at e.update (app.js:1:470762)
    at e.dispatchTransactions (app.js:1:467223)
    at e.dispatch (app.js:1:469370)
    at mB (app.js:1:1652494)

and of course the highlight disappear. We do have a RangeError here...

[mProjectsCode]

I wanna use this to test out how good copilot performs. If it does badly, I will try to fix this manually.

[mProjectsCode]

Should be fixed in 0.7.3

[Seagull2004]

idk, i've tried to update to 0.7.3 but not only it does not highlight the inline code at all but the code in the block is not colored by shiki, i can see the default color being applied to the code words. I've tried to close and reopen obsidian a couple of times but it does not seem to help. I've restore the 0.7.0 and everything turn working again.

[mProjectsCode]

Strange. Can you share the exact note content in which this occurs? Do you use any other plugins or themes? Does the issue persist with them disabled?

[Seagull2004]

So, i've create a completely empty vault, with 0 plugin a part of shiki, and also 0 css snippets. What i get is this:

If i reload the vault with the command "reload without saving" it does color the syntax but if i try to write brand new code, shiki does not color it, however, with the same environment and shiki v0.7.0 everything works correctly.

No error in the console anyways.
I don't really know what is going on...