vscode-neovim: [INFO] wrong CWD when using Dev Containers (extensionKind = "ui")
Check the following:
- I have tried setting
vscode-neovim.neovimCleanin VSCode settings and restarting VSCode. - I have read the vscode-neovim docs.
- I have searched existing (closed!) issues.
Neovim version (nvim -v)
v0.10.1
Operating system/version
Mac 14.4.1
Problem (including log messages)
On a fresh setup with a Dev Container Neovim sets the CWD to /. This prevents e.g. tab path completion working when opening new files.
Steps To Reproduce
- Open a project with Neovim and Dev Container Extensions
:followed bylua print(vim.fn.getcwd())- Output is
/
Expected Behavior
I expect the reported working directory to be the root of the project I am working in.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 17 (1 by maintainers)
This issue has good info though so we can mark it as blocked and keep it open?
Yes, true, but that special case would cover essentially all of Dev Container usage, as the remote workspace is a volume mount of the local workspace - so they are guaranteed equivalent under normal operation. I’m not sure if Dev Container usage alone would be sufficient motivation to implement such a feature, though.