Describe the solution you'd like Automatically generate.vim/coc-configuration.jsonforcoc.nvimusers based on the same rules used to generate it for vscode. Describe the drawbacks of your solution Not all developers usecoc.nvimand not all developers usevscode. The sdk could be extended with addit...
I have been using the NvChad configuration for neovim for a while after switching from VSCode. As I am new to configuring vim I took help from an youtube video. [This is the video my setup is based upon: ] (https://youtu.be/4BnVeOUeZxc?si=Xatala9e71x0eRtC). But as of now nu...
Wrtdisplayvsforeground, I feel we should go withforegroundas many of the best-known develoepr tools likealacritty,iTerm2,VS Codeall use it. In vim we also seefgas the shortcut forforeground. For individual attributes, I preferbackground: :blueover:blue_backgroundbecause it could be hard to ...
It is also possible to write a specific extension to auto-associate the schema. The drawback is that specific IDE extensions must be written for each IDE that you want to support. Hopefully, for some of them, there is a specific API to do it. For instance,vscode-yamlis one way y...