Closed vi closed 11 years ago
Which branch?
32d28393c1f072d4960d7a899775dcf74f7bf7ca
Note: the freeze itself is because of stale FUSE filesystems mounted somewhere. The question is that Enki does all that in foreground.
It is common practice to be prepared for network peers fail. I.e. if Enki loads some info from remote network server via TCP, it will use threads, async io etc to make the process fail safe. But, when Enki works with files, it will believe, that file system calls won't freeze. If I made code FS freeze safe, it will be too complicated.
Won't fix
I meant "Compete symbol under cursor" (which is Ctrl+P in Vim and probably Ctrl+Space in Enki), but it probably tried to show "Print..." dialog...
Probably Ctrl+P should not be this disruptive and should prepare printing in background.