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
In an open neotree float, when trying to move a file in the directory structure up one level using double dots (..), the directory tree after the move shows the double dots as its own directory instead of refreshing.
Manually refreshing neotree with (R) and closing and reopening the directory tree does not refresh/resolve the tree resulting in the double dot folder persisting.
The actual directory tree on the file system does not have a double dot folder and the tree correctly reflects the move.
Screenshots, Traceback
Neotree float window after moving using double dots:
Moving a file to another directory using double dots:
Correct directory structure present on fs:
Steps to Reproduce
Open a project with a directory structure at least 3 levels deep with multiple directories
Navigate to a file at least two levels deep
Move the file to a sister directory using the double dot notation (one level up, and then one level down)
After the move Neotree will show a double dot folder (..) in the current directory and represent the folder structure of the upper level directory in the new double dot folder. The sister folder (target dir) will also be opened in the double dot directory and the moved file will show up there
Expected Behavior
It should move the file using the notation (currently performs this function correctly)
Then refresh the directory tree in the current directory (source dir)
Then resolve and open the target directory (optional, but I assume this was the intended behaviour)
Your Configuration
-- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
-- add any other plugins here
}
localneotree_config= {
"nvim-neo-tree/neo-tree.nvim",
dependencies= { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim" },
cmd= { "Neotree" },
keys= {
{ "<Leader>e", "<Cmd>Neotree<CR>" }, -- change or remove this line if relevant.
},
opts= {
-- Your config here-- ...
},
}
table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
Neovim Version (nvim -v)
0.10.0
Operating System / Version
macos 14.6.1
Describe the Bug
In an open neotree float, when trying to move a file in the directory structure up one level using double dots (..), the directory tree after the move shows the double dots as its own directory instead of refreshing.
Manually refreshing neotree with (R) and closing and reopening the directory tree does not refresh/resolve the tree resulting in the double dot folder persisting.
The actual directory tree on the file system does not have a double dot folder and the tree correctly reflects the move.
Screenshots, Traceback
Neotree float window after moving using double dots:
Moving a file to another directory using double dots:
Correct directory structure present on fs:
Steps to Reproduce
Expected Behavior
Your Configuration
The text was updated successfully, but these errors were encountered: