Live data from Hacker News

Onivim 2 – A retro-futuristic modal editor

onivim.io

31–40 of 78 posts

Re: Onivim 2 – A retro-futuristic modal editor

#31
post #8
post #4

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.

Performance

Re: Onivim 2 – A retro-futuristic modal editor

#34
post #9

>combining the modal ergonomics of Vim, the quick and responsive feel of a native app but, but... vim is a native app?

It is because this is Onivim version 2. The first version was based on VScode, which was not native.

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

#36
post #23

In what sense is "retro-futuristic"? Colour scheme?

I think vim is the retro part...

Sorry, I was just joking :-)

I find funny that they label modal editing, or vim compatibility, or whatever they want to achieve as a retro thing.

Re: Onivim 2 – A retro-futuristic modal editor

#37

Why do modern editors have minimaps now? Do people actually find them useful?

I agree, it's a waste of screen estate and focus estate, I can't see the benefit of a minimap. I usually use imenu in Emacs so any definition is 0.1s away with a keypress

Re: Onivim 2 – A retro-futuristic modal editor

#39

Why 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.

This can be done by colorbands on the scrollbar though
Post reply on HN