Nvim crashes when file explorer is opened for code bases with many files and folders about vapournvim HOT 24 CLOSED

Is that file getting edited by some other program?

from vapournvim.

Sorry, closed by mistake

from vapournvim.

No, it is not being modified by any other program

from vapournvim.

what happens if you do :recover?

from vapournvim.

It says no swap file found for file name..

from vapournvim.

Is it a very big file?

from vapournvim.

I am suspecting that it has something to do with gitsigns,

from vapournvim.

why?

from vapournvim.

from vapournvim.

Try removing the plugin and then packersync

from vapournvim.

If you have some time can you join me on this zoom link https://andela.zoom.us/j/92299011529

from vapournvim.

I can't use zoom rn.

from vapournvim.

ok

from vapournvim.

Did removing the plugin work?

from vapournvim.

How do I remove it? It is not in my user-config

,

from vapournvim.

Just remove it from vapour/plugins/init.lua and in the main init.lua file also there is one require gitsigns config

from vapournvim.

Yes, I took out gitsigns and it is still happening. I also have this diagnostic error message showing up. I even took out lvim-tree and I am still having the same errors.

.

from vapournvim.

Also is there a reason why I get the error, when I enable Compe in line 16?

from vapournvim.

try deleting whatever changes you made and try git pull now

from vapournvim.

ok

from vapournvim.

So I reinstalled vapour nvim, without adding any config inside my user-config and there was no issues until I enabled plugins in my user-config and the error started again.

Also is there a reason why I get the error, when I enable Compe in line 16?

But why do I still have this error when I enable Compe?

from vapournvim.

So I commented out all my activated language servers in user-config and the errors disappeared. So I am going to activate them one after the other to find the culprit that is causing the errors.

from vapournvim.

I found the one Vapour.language_servers.pyright.enabled = true pyright is the problem. You can replicated the issue by enabling pyright, and then open up any source code with folders, then open press space e to open the explorer and select a python file then try navigating the file with the arrow keys, you will see the nvim-tree will automatically open up the folder tree. In a code base with a lot of folders nvim will crash.

from vapournvim.

Use pyls. It works better with python files than pyright. And can this issue be closed now?

from vapournvim.