Describe the bug
Currently the arguments are sent as is, along with guest_cwd, assuming guest_cwd/argv will give the correct absolute path. However if the user has a plugin/autocmd that automatically changes the cwd base on, for example .git or whatever, then this assumption is broken
Expected behaviorsome_dir/sub_dir/some_file should be opened instead
Screenshots
If applicable, add screenshots and/or videos to help explain your problem.
Desktop (please complete the following information):
OS - Pop!_OS 22.04 LTS
Neovim Version - v0.10.0-dev-541+g96b94f8d7
Additional context
One solution is of course to make sure these autocd plugins do not load and activate too early, but then ideally the documentation of this plugin would reflect this requirement.
The more robust solution is to properly fully resolve filepaths (absolute) on the guest side, perhaps we should use the names from the buffers that are automatically opened by neovim?
Describe the bug Currently the arguments are sent as is, along with
guest_cwd, assumingguest_cwd/argvwill give the correct absolute path. However if the user has a plugin/autocmd that automatically changes the cwd base on, for example.gitor whatever, then this assumption is brokenTo Reproduce This is the autocd code I use, which is set before
lazy.setup{}even https://pastebin.com/7uq31x2acd some_dirwith a.gitcd sub_dir && nvim some_filesome_dir/some_fileExpected behavior
some_dir/sub_dir/some_fileshould be opened insteadScreenshots If applicable, add screenshots and/or videos to help explain your problem.
Desktop (please complete the following information):
Additional context One solution is of course to make sure these autocd plugins do not load and activate too early, but then ideally the documentation of this plugin would reflect this requirement.
The more robust solution is to properly fully resolve filepaths (absolute) on the guest side, perhaps we should use the names from the buffers that are automatically opened by neovim?