- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 616
Reuse Buffer #1895
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
Comments
Would also be cool to make a configurable synchronization of currently focused file across different |
That's a larger issue #457 |
@alex-courtis is there any update on that, i think i am facing an issue related to that feature. When i am on a second tab with a buffer loaded in the main tab window (1 window, 1 buffer loaded in the window), if i do :e {dir} and select file from the tree, the tree closes, the tab closes too and i am brought back to the first tab (prev tab), and the file i selected from the tree is not loaded / opened at all. Ideally i would like the file (buffer to be loaded) to be opened in place of the file explorer, i.e not close the window (and consequently the tab) but rather use that window to show the file. |
Does |
@gegoune indeed, is it safe to replace the default on CR = "edit" action with that one by default, what are the differences and possible implications ? I have also by default configured quit_on_open = true, could that also be interfering badly ? |
I can't think of downsides to any of these. You can override default mappings however you like. |
The original motivation for this enhancement is no longer valid following the change to legendary to use the new API Please report your findings @asmodeus812 ; I'll close this one if the above solution meets your needs. |
Let's track this at #457 |
nvim-tree buffer will be wiped on window close as
bufhidden=wipe
One buffer exists per tab:
name
"NvimTree_" .. vim.api.nvim_get_current_tabpage()
buftype=nofile
filetype=NvimTree
The buffer could be reused when nvim-tree is reopened.
Context: #1858 (comment)
The text was updated successfully, but these errors were encountered: