Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NvimTree changes root in the other tab after it is reopened #1978

Closed
carljohnson93 opened this issue Feb 7, 2023 · 3 comments
Closed

NvimTree changes root in the other tab after it is reopened #1978

carljohnson93 opened this issue Feb 7, 2023 · 3 comments
Labels
bug Something isn't working reproduced Issue confirmed

Comments

@carljohnson93
Copy link

Description

When nvim-tree is opened in one tab, then in the other and I change directory with <c-]> there, then go back to previous tab and reopen nvim-tree it loads the directory which I cded into from the other tab.

Neovim version

NVIM v0.8.1
Build type: Release
LuaJIT 2.1.0-beta3

Operating system and version

Artix Linux latest release, also tested on macOS 10.15.7

nvim-tree version

02fdc26

Minimal config

vim.cmd[[
call plug#begin()

Plug 'nvim-tree/nvim-tree.lua'

call plug#begin()
]]

require('nvim-tree').setup()

Steps to reproduce

  1. nvim
  2. :NvimTreeToggle
  3. :tabnew
  4. :NvimTreeToggle
  5. cd into any directory with <c-]>
  6. :tabprev
  7. :NvimTreeToggle
  8. :NvimTreeToggle

Expected behavior

Expected for nvim tree to reopen its window and load same directory I was in just before closing it in this tab

Actual behavior

nvim-tree loads the last opened directory, in this case the one we cded into from the other tab

@carljohnson93 carljohnson93 added the bug Something isn't working label Feb 7, 2023
@alex-courtis alex-courtis added the reproduced Issue confirmed label Feb 11, 2023
@alex-courtis
Copy link
Member

See #1960

@alex-courtis
Copy link
Member

Tracked at #457

@alex-courtis
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working reproduced Issue confirmed
Projects
None yet
Development

No branches or pull requests

2 participants