klonk VS vim-lsp

While surfing the web I came across this blog post: Resolving the Great Undo-Redo Quandary.

Resolving the Great Undo-Redo Quandary\ (31 comments)

My goofy lil' homemade editor does it this way: If you go back in the past and change it, the future becomes the past. This might sound confusing, but effectively it means that the undo stack contains the actual history of "what happened". This means you can hop to any past or future state linearly with undo & redo alone. I just find this easier than navigating tree GUIs and things that aren't worth the trouble to me. It can still lead to a bit of mental gymnastics in extreme cases.

https://github.com/zaboople/klonk

Note that in theory this can cause an exponential growth of the undo/redo stacks because it makes an upside-down copy of the future when you change the past; but in practice it's never been an issue.

I was thinking of adding a feature to navigate back to "last change-the-past", which wouldn't be hard.

It at least makes more sense than most science fiction time-travel plots...

Has anybody managed or got an idea how to make SonarLint Language Server work with e.g. vim-lsp?

You need to configure a language server. For C++ it's a bit tricky, so good luck with Go. There are other plugins that provide semantic highlighting using LSP, for example https://github.com/prabirshrestha/vim-lsp (I didn't try it, but it seems good).

ALE can use LSP as well. And if you are using vim-lsp, you can use the same instance of server for both with vim-lsp-ale bridge plugin.

I feel the same way. Not a one-liner but the smallest config LSP plugin I've found is vim-lsp. It works in both Vim and Neovim.

The only major feature that Neovim still has is a built in LSP client. But I find the built in Neovim LSP client is unusably buggy, you're much better off using any of the other LSP plugins. What I use is vim-lsp, but I've tried all of the major lsp client, they are all significantly better than the built in Neovim LSP.

As for install/configuration, all you need is the latest Vim, the plugins I mentioned, and that bit in your vimrc. You can do a bit better than that if you copy the entire config with mappings from the vim-lsp GitHub page.

I have a problem with Deoplete and Vim-LSP completion (Python's Pylsp and Jedi-Language-Server). The suggestion is much less, and it also misses a lot of opportunities to suggest compared to Deoplete-Jedi, which literally defeats the former by a large margin. Is there a setting to make this duo works like deoplete with deoplete-jedi?

- add the [prabirshrestha/vim-lsp](https://github.com/prabirshrestha/vim-lsp) plugin and config to your `.vimrc` (note: `pylsp` is *not* necessary).