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
Hi, I tried looking through your configuration for kitty and I noticed that my syntax highlighting (comments being greyed out for example) is not present in specifically and only the files in this repo. Any other kitty configuration files I have or have seen don't have this issue.
I tracked it down and it turned out to be the modeline:
# vim:ft=kitty
This didn't trigger the builtin vim.filetype match anymore on *.conf files in my Neovim, because the file type was overridden by it.
A quick side-by-side:
With :set ft=kitty:
_With :set ft=conf:
This does sadly highlight color codes incorrectly, however not having any highlighting at all is kind of intrusive, and because of this my question is: Why did you choose to add a modeline for an unknown filetype?
The text was updated successfully, but these errors were encountered:
Hi, I tried looking through your configuration for kitty and I noticed that my syntax highlighting (comments being greyed out for example) is not present in specifically and only the files in this repo. Any other kitty configuration files I have or have seen don't have this issue.
I tracked it down and it turned out to be the modeline:
This didn't trigger the builtin
vim.filetype
match anymore on*.conf
files in my Neovim, because the file type was overridden by it.A quick side-by-side:
With

:set ft=kitty
:_With

:set ft=conf
:This does sadly highlight color codes incorrectly, however not having any highlighting at all is kind of intrusive, and because of this my question is: Why did you choose to add a modeline for an unknown filetype?
The text was updated successfully, but these errors were encountered: