eyalk5

See https://vi.stackexchange.com/questions/26939/how-to-avoid-losing-your-viminfo-command-history-and-so-on-on-abort for a vimscript mitigation.

NVIM is free of this bug btw. I think it is bug of vim.

I actually have a solution to this. I use FZF (old implementation). But if you can convert it to leaderf , it would be nice. https://github.com/eyalk5/.vim see .vimrc in `:autocmd...

Duplicate https://github.com/Yggdroot/LeaderF/issues/536

I wish to say that specifically doing vimgrep is really slow. Doing verbose=15 I noticed that there is this line , written once: `Executing BufReadPost Auto commands for "*" autocommand...

Mitigation for vimgrep : ``` function! Matches2(a) :set eventignore=all execute ":vimgrep " . '/'.a:a . "/j **/*" :set eventignore= :copen endfunction```


Indeed. When I simply run pyls from command line, it seems to be working. eyalkarni@xxxx:~$ pyls -v 2019-02-25 01:32:05,154 UTC - INFO - pyls.python_ls - Starting PythonLanguageServer IO language server

Thank you. It seems to be working.

OK, it doesn't set the change. When I tried to set (in activate): ``` oni.language.python.languageServer.command="python" oni.language.python.languageServer.arguments= ["-m", "pyls"] ``` then it raises an error when trying to upgrade config.js. And...