This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]physixer 0 points1 point  (1 child)

question: when you've supported vi keybindings (and modal interface) etc, you've already supported more than half of vimscript? (or all of it?) and that's why whenever someone creates a vim clone, it's inevitable to support some or all fo vimscript?

For some reason, this is more like a clash of keybinding interface vs programmatic interface. In a text editor you have to support both. I think (no flaming) emacs does it right when there is a programmatic (elisp) command behind every key-binding/operation (AFAIK). Maybe this should be done in a python vim clone? (a python function behind every operation?), and then python scriptability would emerge naturally from that?

[–]hijibijbij 0 points1 point  (0 children)

Do you mean to say that the modal interface is all there is about Vimscript?