If there is a better syntax option out there, I would be happy see that go upstream instead. I am not a {neo-,}vim user myself, so I don’t really feel like I’m the one to do the maintenance on this work. If the amount of change on the vim-nix syntax file is any indication, though, there shouldn’t be too much effort involved in being the one to answer the call when PRs come in.
Edit: Moved to #dev from #learn since I think it is more appropriate
Neovim gets runtime patches from vim so upstreaming should go through vim first. Neovim also has some experimental support for treesitter and there is a nix grammar. Wont be upstreamed though.
Neovim gets runtime patches from vim so upstreaming should go through vim first. Neovim also has some experimental support for treesitter and there is a nix grammar. Wont be upstreamed though.
Yes! That’s why I think upstreaming to vim is the best first thing to do.
What’s your motivation then ?
I have a few motivations:
Marketing - for Nix to be mainstream, it needs to start being in the default options of various platforms. Simple editor support seems like a nice place to start
I sometimes have to use vim on remote machines where I don’t have a config. Editing Nix files sans syntax highlighting usually means set ft=haskell and living with it.
It would be nice for vim users wanting to try nix out without commiting to much