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
After upgrading to vscode 1.74.2, I start observing a behavior change when openning another buffer with :e or :split in current buffer.
VSCode version: 1.74.2
VSCodeVim version: 1.24.3
Operatiing System: Windows 10
How to reproduce:
In VSCodeVim, open up terminal with working directory as /my/path/
Open up a buffer: code dir/foo.txt
In buffer foo.txt, do :split <tab>, it just searchs and autocomplets files within /my/path/dir instead of /my/path.
From this observation, it behaves like the variable autochdir is set so the cwd is changed.
Behavior in native
Things are different in native vim if I do it directly from vscode terminal.
Workaround
Currently autochdir is not supported yet thus there's no way to change this behavior on VSCodeVim.
The text was updated successfully, but these errors were encountered:
After upgrading to vscode 1.74.2, I start observing a behavior change when openning another buffer with :e or :split in current buffer.
VSCode version: 1.74.2
VSCodeVim version: 1.24.3
Operatiing System: Windows 10
How to reproduce:
/my/path/
code dir/foo.txt
foo.txt
, do:split <tab>
, it just searchs and autocomplets files within/my/path/dir
instead of/my/path
.From this observation, it behaves like the variable
autochdir
is set so thecwd
is changed.Behavior in native
Things are different in native vim if I do it directly from vscode terminal.
Workaround
Currently
autochdir
is not supported yet thus there's no way to change this behavior on VSCodeVim.The text was updated successfully, but these errors were encountered: