Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignoring $NVIM_APPNAME to generate files and directories #5070

Closed
uga-rosa opened this issue Jun 30, 2024 · 1 comment · Fixed by #5073
Closed

Ignoring $NVIM_APPNAME to generate files and directories #5070

uga-rosa opened this issue Jun 30, 2024 · 1 comment · Fixed by #5073
Assignees

Comments

@uga-rosa
Copy link

uga-rosa commented Jun 30, 2024

Result from CocInfo

Describe the bug

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

  • Create file mini.vim with:

    set nocompatible
    set runtimepath^=/path/to/coc.nvim
    filetype plugin indent on
    syntax on
    set hidden
  • 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.

@fannheyward fannheyward self-assigned this Jul 4, 2024
fannheyward added a commit that referenced this issue Jul 4, 2024
@fannheyward
Copy link
Member

coc-settings.json is located in stdpath('config'), other files created by coc.nvim are located in ~/.config/coc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants