OK Version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0]
Pynvim ~
OK Version: 0.4.3
Ueberzug (optional) ~
WARNING Ueberzug is not found in Python Lib
RPC ~
OK RPC echo: Neovim send "Give me five!" and receive "Give me five!"
**Describe the bug**
After selecting a file in ranger, cwd changes from the original directory where you opened neovim to the home directory.
**To Reproduce using `nvim -u mini.vim`**
Example:
`cat mini.vim`
```lua
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({
"git",
"clone",
"--filter=blob:none",
"https://github.com/folke/lazy.nvim.git",
"--branch=stable", -- latest stable release
lazypath,
})
end
vim.opt.rtp:prepend(lazypath)
require('lazy').setup({
{
'kevinhwang91/rnvimr',
config = function()
vim.keymap.set('n', '<leader>e', '<cmd>RnvimrToggle<cr>')
end,
init = function()
vim.g.rnvimr_enable_picker = 1
end
}
})
Steps to reproduce the behavior (using /home/<user>/foo/bar as the example directory):
open the directory with nvim . (should open in netrw)
open a file
run :lua print(vim.loop.cwd())
see expected /home/<user>/foo/bar output
press <space>e to open rnvimr (leader is mapped to space)
open a file different from the one you opened previously
run :lua print(vim.loop.cwd())
see that it prints /home/<user> instead of the expected directory
Expected behavior
Should maintain proper cwd instead of having this bug
Video reproducing this bughttps://www.youtube.com/watch?v=dFPpnFkjCUc (apologies for the terrible pink background. This is related to my terminal colorscheme conflicting with neovim's defaullt colorscheme and shouldn't affect this issue)
nvim --version:Run :checkhealth for more info
rnvimr: health#rnvimr#check
OS ~
Ranger ~
Python ~
Pynvim ~
Ueberzug (optional) ~
RPC ~
Steps to reproduce the behavior (using
/home/<user>/foo/baras the example directory):nvim .(should open in netrw):lua print(vim.loop.cwd())/home/<user>/foo/baroutput<space>eto open rnvimr (leader is mapped to space):lua print(vim.loop.cwd())/home/<user>instead of the expected directoryExpected behavior Should maintain proper cwd instead of having this bug
Video reproducing this bug https://www.youtube.com/watch?v=dFPpnFkjCUc (apologies for the terrible pink background. This is related to my terminal colorscheme conflicting with neovim's defaullt colorscheme and shouldn't affect this issue)
Additional context Ranger version: 1.9.3 Python version: 3.10.6 Locale: en_US.UTF-8