-
Notifications
You must be signed in to change notification settings - Fork 550
Open
Labels
A-contributor-onboardingArea: contributor on-boarding advice (e.g. for new contributors)Area: contributor on-boarding advice (e.g. for new contributors)C-enhancementCategory: enhancementCategory: enhancement
Description
https://rustc-dev-guide.rust-lang.org/building/suggested.html#neovim describes three ways to use neovim.
- Using neoconf.nvim and the vscode settings.
- using coc.nvim
- using the manual config.
Option 1 mostly seem to work just fine, except neovim not recognizing or replacing ${workspaceFolder}
(see also) #2259 (comment)
I ended up replacing it with the absolute path. I'm not super experienced with these configs, so not sure if neovim has another name for it, if we should ask Neovim devs to add support, or (probably a good addition either way) add a note to the docs which tells users to use the absolute path.
At least option 3. also defines a function to recognize and handle the workspacefolder, but it's not clear that users have to handle it manually when using neoconf.
Metadata
Metadata
Assignees
Labels
A-contributor-onboardingArea: contributor on-boarding advice (e.g. for new contributors)Area: contributor on-boarding advice (e.g. for new contributors)C-enhancementCategory: enhancementCategory: enhancement