3 ms·

For what it's worth, you can also write Vim extensions in Python. It's got access to all the same stuff as Vimscript. I would argue that Python is the better la

For what it's worth, you can also write Vim extensions in Python. It's got access to all the same stuff as Vimscript. I would argue that Python is the better language when compared to elisp (even if one believes CL or other full-blown Lisp or Scheme variants are superior to Python). I'm not saying that makes vim a better editor than emacs. Just pointing out that vim has other options for extending. Also, I use vim and haven't found emacs to be more productive; in my college days I tried emacs, in earnest, for a few months. I came back to vim eventually, and haven't felt compelled to give emacs another go since.

terhechte 13y ago
The Emacs/ELisp API, however, is far better. If we assume for a moment that ELisp and Python are, for the act of writing a editor extension, in similar good shape. Then it is still easier to write a good plugin with elisp for emacs than with python for vim, because the API that emacs offers for the integration of scripts is really, really fantastic. Vim doesn't offer anything like that.
eichin 13y ago
For that matter, you can write emacs extensions in python, using Pymacs; given that it's marshalling objects to and from a subprocess over a pipe, it breaks when anything gets asynchronous, but lately when I've gone beyond "customization" to "actual code", pymacs has made it so much easier that after a few decades with emacs, I really want an open source editor with emacs' richness (and bindings) and python as a first-class extension language.