-
Notifications
You must be signed in to change notification settings - Fork 255
Performance issue/unstable with recent commits? #767
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
I've completely stopped using neo-tree since the last few days for the same reasons, it's becoming very glitchy and lots of issues have been popping up... |
Using neo-tree with sessions is messy too... |
@cseickel : can you pump up a bit with new commits? currently not stable for usage. |
Hi! A few days ago, I pushed #748 and #761 to clean up invalid buffers caused by session restore, which could cause bugs as mentioned in #740. This might be the cause of the bugs that you have seen, and I'm terribly sorry for that 😞. However, I can't seem to reproduce the issue that you mentioned. Could you provide me with some steps on how to do this? |
@nhat-vo : I used neotree with persisted.nvim as i mentioned in 1st post with linked issue. so neotree would not stored in the saved session, but i got issue that all buffers deleted and neotree randomly restored and sometime not. also i'm observing cursor shifted at the end of buffer (most bottom left) and some kind of error message after doing I use nvim-nightly and latest neotree and persisted.nvim. like i mentioned, the previous commit from 2022 work for me and i currently at that commit to prevent current bug. There's smth that also affected my startup time with neotree, reached to ~150ms and if i use previous commit, never above 100ms (with lazy.nvim profiling) |
@tmpm697 Could you provide a minimal config, please 😄? |
just tried with all latest neotree and persisted.nvim again, got this error:
my neotree config:
|
@tmpm697 I used the neotree config that you sent, combined with {
"olimorris/persisted.nvim",
config = function()
require("persisted").setup({
autoload = true,
on_autoload_no_session = function()
vim.notify("No existing session to load.")
end,
})
vim.api.nvim_create_autocmd({ "User" }, {
pattern = "PersistedSavePre",
group = group,
callback = function()
pcall(vim.cmd, "bw neo-tree")
end,
})
end,
}, Then I tried opening |
I see. The issue here is that #761 added a hook to close any neo-tree buffer on session load, and this also closes the neo-tree buffer that you loaded in |
I'm using Workspaces Nvim and using this:
and this is what I get: 2023-02-24_17-05-21.mp4This works perfectly with Nvim Tree: 2023-02-24_17-08-42.mp4Neo Tree closes itself automagically... |
@charbelnicolas #771 (just got merged into |
@nhat-vo main LGFM. |
This did not fix the issue I'm having. IMO, neo tree shouldn't close anything automagically because it leads to these kinds of issues. UPDATE: Hmm, now that I think about it, I never changed branches, lol |
@charbelnicolas So was the bug fixed for you? The closing was just there to avoid any collision (in #740), which might cause neo-tree to behave incorrectly. |
Yes, thank you |
Closing as solved. |
this plugin became unstable with recent commits, the last stable one i can actually use is
d9e50c185f5728d8cb64943566449180b2903fd4
-- that's from last dec 2022.recent ones cause my buffer
flick
when use with persisted.nvim to save/restore session. check this: olimorris/persisted.nvim#51The text was updated successfully, but these errors were encountered: