Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why ft=kitty? #16

Closed
dtomvan opened this issue Feb 14, 2023 · 3 comments
Closed

Why ft=kitty? #16

dtomvan opened this issue Feb 14, 2023 · 3 comments

Comments

@dtomvan
Copy link

dtomvan commented Feb 14, 2023

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:
without the modeline, comment are not greyed out as they would

_With :set ft=conf:
with the modeline, greying out comments and color codes because of the # syntax for both colors and comments

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?

@nekowinston
Copy link
Contributor

The reason for vim:ft=kitty is vim-kitty.

@dtomvan
Copy link
Author

dtomvan commented Feb 14, 2023

Ah. Alright, thank you for your explanation and sorry for bothering you

@dtomvan dtomvan closed this as completed Feb 14, 2023
@nekowinston
Copy link
Contributor

No worries, I can see how it's opinionated. But when you have a longer Kitty config, that plugin is quite nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants