Falling to first folder on path, e.g: nvim project/packages/docs, shows docs first and when open a file falls to project.

[Uanela]

Description

On 09/08 I opened an issue (#3180 ) about an error I was facing and it was solved simply by going back to commit "a9156c0" and the error was gone.

Today just noticed this new bug, is worth mentioning that I wasn't even using commit "a9156c0" before finding the bug from issue #3180.

Now when I do the following:

$ nvim arkos/packages/docs

It will open nvim and show nvim tree with docs files, but all of sudden when I try to open a file or folder it falls back to files from arkos folder.

I simply solved it by going back to a commit from 3 weeks ago, commit "543ed3c", and it is working fine as I used to work with it.

I saw Multi Instance refactor and I am interested into contributing but currently I am not that aligned to lua maybe by the time I finish grasping it the refactor is still up, I am currently working on nodejs framework for RESTful API built on top of express and prisma consider checking https://github.com/uanela/arkos.

Neovim version

NVIM v0.11.2
Build type: Release
LuaJIT 2.1.1748459687

Operating system and version

macOS Sequoia 15.4

Windows variant

No response

nvim-tree version

commit a9156c0 (have the problem), commit 543ed3c (solution so far).

Clean room replication

return {
 "nvim-tree/nvim-tree.lua",
 -- commit = "a9156c0",
 commit = "543ed3c",
 dependencies = { "DaikyXendo/nvim-material-icon" },
 keys = {
  { "<leader>e", function() require('nvim-tree.api').tree.focus() end, desc = "Focus file explorer" },
  { "<C-b>", "<cmd>NvimTreeToggle<cr>", desc = "Toggle file explorer" },
 },
 config = function()
    local tree_opened = false
    require("nvim-tree").setup({

     renderer = {
       icons = {
         webdev_colors = true,
       },
       group_empty = true,
     },
     sort_by = "case_sensitive",
     view = {
       width = 30,
       side = "right"
     },
     filters = {
       dotfiles = false,
     },
     update_focused_file = {
       enable = true,
       update_cwd = false,
       update_root = false,
       ignore_list = {},
     },
     on_attach = function(bufnr)
       local api = require("nvim-tree.api")

       if not tree_opened then
          tree_opened = true
          api.tree.change_root_to_node()
       end
      api.config.mappings.default_on_attach(bufnr)
      
      vim.keymap.set('n', '<C-j>', function()
        local node = api.tree.get_node_under_cursor()
        if node.type == "file" then
          local last_win = vim.fn.winnr('#')
          if last_win > 0 and vim.api.nvim_win_is_valid(last_win) then
            vim.cmd(last_win .. "wincmd w")
            vim.cmd("edit " .. node.absolute_path)
          else
            api.node.open.edit()
          end
        end
      end, { buffer = bufnr })
      
      end,
   })
 end,
}

Steps to reproduce

1. Simply configure your nvim with Lazy.nvim and the use the configuration above for your nvim-tree
2. $ nvim some/nested/folder

Expected behavior

Should show the content of the latest file/folder on the path and keep it even though I interact with it except when I trigger to explore outer folders.

Actual behavior

Shows the content of the last file/folder on path but as soon as I interact with some file/folder on the tree it quickly shows the content of the first file/folder of the path.

[alex-courtis]

I saw Multi Instance refactor and I am interested into contributing but currently I am not that aligned to lua maybe by the time I finish grasping it the refactor is still up, I am currently working on nodejs framework for RESTful API built on top of express and prisma consider checking https://github.com/uanela/arkos.

Your contributions would be most gratefully appreciated!

• CONTRIBUTING.md
• Wiki: Development

Honestly, I've just put the multi instance project on hold #2255, as it's at an impass and needs a rethink.

If you're looking to contribute, there are many bugs and features to work on. See the PR Please issue list.

[alex-courtis]

I think I see the problem:

- or enter on root:

This has been long-standing behaviour, back to v1.0.0

The tree does not retain the opened state of folders when you create a new tree. Moving up a directory or changing directory will create a new tree.

Remembering that state is a feature that would be of great value!

[Uanela]

@alex-courtis exactly this behavior.

I just started using another commit as I shared and the problem is just gone.

Let's get a good grasp of lua and in a couple of weeks or 1 to 2 months I can start contributing to this project.

Thank you for your feedback.

[alex-courtis]

Let's get a good grasp of lua and in a couple of weeks or 1 to 2 months I can start contributing to this project.

You might read Programming in Lua (free online) from the language's author. It's short but it covers everything with good examples.

The Reference Manual is very dry and not a good introduction to the language.

[Uanela]

Let's get a good grasp of lua and in a couple of weeks or 1 to 2 months I can start contributing to this project.

You might read Programming in Lua (free online) from the language's author. It's short but it covers everything with good examples.

The Reference Manual is very dry and not a good introduction to the language.

Thanks man, see you soon.

[Uanela]

@alex-courtis just finished studying Lua, did this in 3 days, I read the book Lua Quick Start Guide by Gabor Szauer.

And I was here looking of what to do next, I just forked the repo skimmed a little bit and I thought maybe I will need to read a little bit about nvim interaction with lua itself (Just my thoughts).

What you think should be the next step for me to be able to easily start contributing into this project.

[alex-courtis]

And I was here looking of what to do next, I just forked the repo skimmed a little bit and I thought maybe I will need to read a little bit about nvim interaction with lua itself (Just my thoughts).

There's not really much reference material available as it's still quite new. :help api.txt describes all the interactions that are available.

Here's an issue you might start with, part of the multi instance project. It doesn't involve much vim interaction, more refactoring. It's do to with changing root :)

#2988

If you'd like a bug or feature to look at instead, let me know.

[Uanela]

Thank you for the onboarding on the multi instance project and for the reference for helping me in getting started with lua on nvim.

Soon enough I'll be back.

[alex-courtis]

Thank you for the onboarding on the multi instance project and for the reference for helping me in getting started with lua on nvim.

It's a pleasure to have you.

Let me know if you have any questions or would like to work on a different issue.

[Uanela]

Hello @alex-courtis I am been doing some stuffs upon the issue you just assigned me (and I am not quite sure if I got it right) I will share it soon so that you can check it.