You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Neovim, $NVIM_APPNAME affects rtp, so the results of stdpath('config'), etc. also change. The configuration file ~/.config/${NVIM_APPNAME}/init.lua will be used, and so on.
However, coc.nvim does not seem to take this into account, and :CocConfig opens ~/.config/nvim/coc-settings.json.
Probably all the files and directories that coc.nvim automatically creates, besides :CocConfig, do not take $NVIM_APPNAME into account as well.
Reproduce the bug
We will close your issue when you don't provide minimal vimrc and we can't
reproduce it
Result from CocInfo
Describe the bug
In Neovim,
$NVIM_APPNAME
affects rtp, so the results ofstdpath('config')
, etc. also change. The configuration file~/.config/${NVIM_APPNAME}/init.lua
will be used, and so on.However, coc.nvim does not seem to take this into account, and
:CocConfig
opens~/.config/nvim/coc-settings.json
.Probably all the files and directories that coc.nvim automatically creates, besides
:CocConfig
, do not take$NVIM_APPNAME
into account as well.Reproduce the bug
We will close your issue when you don't provide minimal vimrc and we can't
reproduce it
Create file
mini.vim
with:Place mini.vim into
~/.config/test/init.vim
Start (neo)vim with command:
NVIM_APPNAME=test nvim
:CocConfig
:echo expand('%')
shows the path of the configration file.Screenshots (optional)
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: