You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, a code block was anything between triple-backtics, including inline
blocks:
some text ```
not a codeblock, but highlighted as one
``` other text
and even if the closing backticks had the wrong indent:
```
this is a code block containing a triple backtick
```
this is still a code block, but Kakoune thinks otherwise
```
Now we use the -match-capture flag to ensure the start and end fences have
exactly the same indent.
Previously, the generic code-block region was defined first, which meant that
it took priority over all the language-specific highlighters. Now we define
the generic code-block highlighting *after* the others, which fixesmawww#2304.
Previously, code-spans were defined as ordinary inline markup, but in Markdown
ordinary formatting doesn't work inside code-spans. Therefore, they are now
regions unto themselves, defined according to section 6.3 of the CommonMark
spec <https://spec.commonmark.org/0.28/#code-spans>, which addresses a comment
on mawww#2111.
System Info
Arch Linux, using the
kakoune-git
package on the AURSteps
Open a markdown file (e.g.
test.md
) and write a fenced codeblock, e.g.Outcome
The
go
code inside of the block is not highlighted as expected. This is the case for all of the languages I've tested (Go, Haskell, and C).This also happens when I run
kak
with the-n
option to ignore my config (so I know it's not an issue caused by my ownkakrc
).Edit: A bit more info -- the markdown codeblock language highlighters are being loaded, as I see them when I type
:rmhl shared/markdown/
.The text was updated successfully, but these errors were encountered: