yaml-companion.nvim VS nvim

You can use https://github.com/someone-stole-my-name/yaml-companion.nvim to get and set the schema for the current buffer. Works out of the box with Kubernetes.

One of the things I was missing in my nvim setup was the ability to choose the schema that yamlls uses in the various buffers. This server also intentionally leaves out some cool features like content aware schema detection and, since I could never get the Schema Store functionality to work when paired with the hard-coded Kubernetes support in the language server… I have converted all the hacky lua I had into this plugin. Sharing it here in case it is useful to anyone https://github.com/someone-stole-my-name/yaml-companion.nvim

Not OP, but I had the same question. I would prefer to manage my nvim config not the NixOS way.

You might also have a look at my recent commit on my "develop" branch https://github.com/Allaman/nvim/commit/1b587f16d074755c94a8692925dfcbf5344fb7d4

Allaman's Neovim Config

In my config I have these lines

From time to time I build my Dockerfile to test if my config would run on a fresh system or if an issue might only be related to my host

It is working for me but I am not aware of any "special" setting I made. here is My cofing maybe you can get an idea. ([go](https://github.com/Allaman/nvim/blob/main/lua/config/go.lua), [lsp](https://github.com/Allaman/nvim/tree/main/lua/config/lsp)]])

There is only one LSP running for in my Neovim My config for reference

Thanks for your inspiration ;) https://github.com/Allaman/nvim/commit/78e32885972947240b0907df6a8a1cceea9fce19

in the last couple of weeks I noticed some Neovim crashes (segmentation faults says my terminal) and I wonder if I am alone? Before that I never had crashes and now at least two a day. Neovim head and here is my config