-
Notifications
You must be signed in to change notification settings - Fork 271
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Did you check docs and existing issues?
- I have read all the docs.
- I have searched the existing issues.
- I have searched the existing discussions.
Neovim Version (nvim -v)
NVIM 0.11.4
Operating System / Version
Windows 10
Describe the Bug
This is a regression of #1468 which was originally fixed in #1650. I have bisected the bug to reappear with Commit e01ca7d or #1799.
Original description:
Trying to reveal a file inside hidden folders while hidden items are not shown results in neotree opening up but not moving anywhere. No note, no error message what is happening and why, nothing. I find this very confusing, and also I think that if I want to reveal a file at that point I don't really care if it's in a hidden or non-hidden folder, I want to see it. Please enable reveal regardless hidden items are shown or not.
Screenshots, Traceback
No response
Steps to Reproduce
- don't show hidden items
- open a file inside a hidden folder
- :Neotree reveal (or reveal_force_cwd)
- neotree opens but "nothing happens"
Expected Behavior
Reveal item regardless if it's in a hidden or non-hidden folder.
Your Configuration
-- template from https://lazy.folke.io/developers#reprolua, feel free to replace if you have your own minimal init.lua
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()
require("lazy.minit").repro({
spec = {
{
"nvim-neo-tree/neo-tree.nvim",
branch = "v3.x", -- or "main"
dependencies = {
"nvim-lua/plenary.nvim",
"nvim-tree/nvim-web-devicons", -- not strictly required, but recommended
"MunifTanjim/nui.nvim",
-- { "3rd/image.nvim", opts = {} }, -- Optional image support
},
lazy = false,
---@module "neo-tree"
---@type neotree.Config?
opts = {
-- fill any relevant options here
},
}
},
})
vim.g.mapleader = " "
vim.keymap.set("n", "<leader>e", "<Cmd>Neotree<CR>")
-- do anything else you need to do to reproduce the issueMetadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working