Open mathieulongtin opened 6 years ago
I pushed a commit to improve filename completion. Can you please update and check it again?
It seems faster, but now it doesn't complete if there are two "/" on the same line, even if they have a space in them.
In a Python comment, it tried to complete a / with function names.
If you type //
it should complete. But if you type / /
it might not complete because completor treats the whole path / /
as a file path.
Sorry for not reporting earlier. It still stalls. It's not my file system, "find / -maxdepth 1" takes 30ms.
I'll try to dig into how it gets the list of files.
Whenever I type a / in Python code, completor stalls for a few seconds while reading a file list.
Digging a little, I switched Filename to "sync = False", this makes the stall more bearable. Either that, or raise the
completion_delay
.Would there be a way filename completer to only kick in after at a few character after the /?