Carl Mueller-Roemer

This problem has a workaround https://github.com/microsoft/vscode-remote-release/issues/3575. Apparently after a VSCode update the cached server doesn't get invalidated properly. Of course this workaround is not nice and should be handled automatically,...

@eliot-akira I'm not quite sure that's the only issue. when I refresh `VSCODE_IPC_HOOK_CLI ` and use 'code --wait' as my git rebase editor, it tells me I need to run...

@eliot-akira yes, that's right, delete the server and restart helped

Thanks for the response. I'm currently trying to set it up, mostly having trouble with the proxy config. I did try 1.1.0 but it seems to be gradle issues. When...

Thank you. I got the proxy working now, I had the http:// in front of the proxy, and gradle sadly doesn't complain, but didn't take it either. That document might...

A link to your guide on `Enterprise Edition` would also be helpful. But some specific information to get going quickly would help usability a lot.

I'm working on 1.0.0 right now, because I want to get the stable release working properly first.

Thank you for the quick response. That was just a copy-paste error. Just in case I tried again and received the same error message.

Hello Luc, I tried all three options I get E117: Unknown function: lh#local_vimrc#lists

Ah, I found if you do this config after Vundle is done it works. It only appears deactivated when done with Vundle. This was a bit surprising since let g:local_vimrc...