Slows down when save and quit changed file

[fitrh]

simplescreenrecorder-2021-01-09_10.00.44.mp4

This is suddenly happen and i don't know what caused them, save and quit (:wq) a changed file give some delay, after disable this plugin, it back normal again.
But this is not happen if doing save(:w) and quit(:q) separately. I use the default configuration from README.

[kyazdani42]

Not sure why this happens. I did not manage to reproduce properly because my computer's too fast. Could you tell me which commit caused the issue ?

[fitrh]

I think since the last commit of neovim, recently i just rebuild my neovim with the latest commit and also update this plugin, the problem still remains, but now, a little bit faster, and it's only happens with :wq, for now, i just stick with :w then :q.

[fitrh]

This is what is looks like from the latest commit of neovim

simplescreenrecorder-2021-01-11_06.08.50.mp4

[kyazdani42]

i meant which commit of nvim-tree introduces this anomaly ?

[fitrh]

I think it's 86944b5, but, isn't that just a renaming ?

[kyazdani42]

don't think it should change anything related to saving. There might be an issue with some async stuff on buf change.

[pesader]

I'm having the same issue. When nvim-tree is loaded, it takes a long time to write a file for the first time in a given session, but the following :w work as expected. For me, nvim freezes on :w as well :wq.

In any case, thank you for developing nvim-tree! Aside from this issue, it's the best explorer plugin I've ever used.

[kyazdani42]

thanks @pesader :)
yes i've seen this happening too on my other computer, i might just push a fix when i have some time

[sbulav]

I had similar issue with vim-startify and g:nvim_tree_follow set to True. For me setting g:nvim_tree_follow to False fixed the issue.

[fitrh]

I had similar issue with vim-startify and g:nvim_tree_follow set to True. For me setting g:nvim_tree_follow to False fixed the issue.

Try this on my build, but the issue still exist

[kyazdani42]

if someone wish to debug this issue, because i'm quite busy at the moment and will not be able to work on this project for at least a month or so.

[kyazdani42]

should be fixed in latest master, can you confirm ?

[fitrh]

Thank you, it's fixed in my machine, can you tell me which commit is that ? i see there are 3 commit from you.

[kyazdani42]

it's been fixed in 42a875aa006239d5b688f56ac37ff58c5aab1b69 !