Earlier quoted context omitted.
Seems that the idea is to implement vscode APIs and use the vscode plugin host and backend system for extensibility.
Why not just write a Vim plugin for VSCode then though? Which already exists.
Onivim 2 – A retro-futuristic modal editor
31–40 of 78 posts
Re: Onivim 2 – A retro-futuristic modal editor
#32>combining the modal ergonomics of Vim, the quick and responsive feel of a native app but, but... vim is a native app?
Re: Onivim 2 – A retro-futuristic modal editor
#33Re: Onivim 2 – A retro-futuristic modal editor
#34>combining the modal ergonomics of Vim, the quick and responsive feel of a native app but, but... vim is a native app?
You also didn't quote the important part. It should reads like this
> the quick and responsive feel of a native app, and the vast extension ecosystem of VS Code.
Essentially, you are in the market for onivim if
- You like vim
- You hate the sluggishness of VSCode
- Your workflow depends on specific VSCode extensions (may be because all your teammates use VSCode?)
Re: Onivim 2 – A retro-futuristic modal editor
#35Re: Onivim 2 – A retro-futuristic modal editor
#36Re: Onivim 2 – A retro-futuristic modal editor
#37Why do modern editors have minimaps now? Do people actually find them useful?
Re: Onivim 2 – A retro-futuristic modal editor
#38Why do modern editors have minimaps now? Do people actually find them useful?
Re: Onivim 2 – A retro-futuristic modal editor
#39Why do modern editors have minimaps now? Do people actually find them useful?
I personally like them for resolving merge conflicts by hand. It really helps just clicking on a section in blueish to instantly jump to a conflict in large-ish files.