coc.nvim uses jsonc as configuration file format, the same as VSCode. It's json that supports comments, like:
To get correct comment highlighting, make sure you use a recent Vim (8.2.3117 or later) or NeoVim (0.6.0 or later) version. Alternatively you can install vim-jsonc (which has built-in support for coc-settings.json), or even simply add:
autocmd FileType json syntax match Comment +\/\/.\+$+
to your .vimrc
or init.vim
.
Use the command :CocConfig
to open your user configuration file, you can create a shortcut for the command like this:
function! SetupCommandAbbrs(from, to) exec 'cnoreabbrev <expr> '.a:from \ .' ((getcmdtype() ==# ":" && getcmdline() ==# "'.a:from.'")' \ .'? ("'.a:to.'") : ("'.a:from.'"))' endfunction " Use C to open coc config call SetupCommandAbbrs('C', 'CocConfig')
Variables would be expanded in string values of configuration, supported variables:
${userHome}
the path of the user's home folder${cwd}
current working directory of vimsome additional variables see:
:h coc-configuration-expand
To enable intellisense for coc-settings.json
, install the json language extension coc-json by:
In your vim.
Checkout :h coc-config
for all built in configurations.
Just like VSCode, each coc.nvim extension can contribute configuration sections, for example:
tsserver
, typescript
and javascript
json
To get detailed options for existing configurations, just try the completion in the file coc-settings.json
:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4