Hacker News Reader

Comment by terhechte | Hacker News Reader

You mentioned elsewhere that VIM bindings are upcoming. I think this product will be an insta-buy for me once there're (reasonably proper) vim bindings. Is there a newsletter or something to know once this feature has landed?

Also as a hint, before you try to re-implement 30 years of VIM bindings and end up with something where everybody misses something, there's a great C library that could be of help:

https://github.com/onivim/libvim

View on HN

As I understand the documentation, libvim would manage and manipulate the buffer, i.e. basically "own" the text. However, Zas (and most other editors) already handle that, and probably would want to keep it that way. Does this still work together with libvim then, that libvim operates on a shared custom data structure, whatever the editor (Zas) provides to represent the buffer?

Thanks for the hint. You can follow us on Twitter @ZasEditor for update announcements.

Seconding that VIM bindings are a requirement for me for what looks like an otherwise amazing editor.

the curse of vim.

Once you've learn vim keybinds and combinations, nothing comes close for productivity.

Once you've learned vim why do you care if any other editor has vim bindings? What can you do with vim-mode ZasEditor that you couldn't do in vim?

vim is not an IDE. You can make it IDE-like with plugins and integrating third-party tools (e.g. for completion, refactoring, debugging), but it is still not one. You may not care, but come on, it's not that hard to understand.

I think there is a difference between features of the editor and editing method. Following your logic - if there is already Notepad, why create TextPad, Atom, Word, VSCode etc...

I'm a heavy user of JetBrains IDEs for most of my development work and use it with the excellent IdeaVIM plugin because modal editing is my preferred input method.

I have all the goodies and features of the full IDE with the keybindings and modal editing muscle memory I've built up over the last 15 years.

Technically I can get Vim to do most of what JetBrains does but that's a very very big hill to climb.

One has a choice between learning enough about Vim to replicate arbitrary workflows/functionality in it, or using other softwares that do those things out of the box and clicking the "Vim mode" check box in the settings.

Both are perfectly valid, but they are going to appeal to different kinds of people, with different priorities.

* pairing/mobing with people who are more familiar with their IDE

* Believe it or not, there are things no vim plugin can do, for example rendering mardown, which Viscose has lots of plugins for that work well

Reply on news.ycombinator.com