Closed kovasap closed 5 years ago
Also, I think the directory tree I'm working on is a network mounted file system. I think it takes so long to do this checking because of the network latency. Is there any way to just disable it all?
I've tried specifying the executable of my linters with g:alepython
You're going to have a lot of trouble with network mounted file systems. My advice is to search through all of the options for the linters you use and disable as many options that cause files to be searched, and try to avoid network mounts if you can. At the moment, there's nothing else that can be done about this.
In the future, ale#command#Run
could be used to perform searches for files in another process, which would mean there would be no more input lag in Vim. This is easier said than done.
Ok. I have a workable state now with specifically chosen linters and
let g:ale_cache_executable_check_failures = 1
!
Information
VIM version NVIM v0.3.3 Build type: Release LuaJIT 2.1.0-beta3
Operating System: Linux
What went wrong
Noticeable lag when typing or doing other actions in vim. Here is a profile.log summary captured when typing a few random words:
Reproducing the bug
Try editing in very large file tree, where vim instance was started at root and you are editing a file ~5-10 directories deep.
:ALEInfo
Any ideas for working around this?