4 ms·

It is a minor sadness that Bram didn't choose a lisp as the vim macro language. But I still love vim...although Ive forgotten more bindings than other editors

• nrr 17y ago
  I'm not actually all that certain I want Lisp as my extension language. Lisp is very, very nice, and while I may have a preference for it, someone else might not. FWIW, MicroEmacs uses an in-house extension language that, while really repulsive to look at at times, gets the job done. That said, I also have a preference for Lua when it comes to more maintream languages, and to boot, there's a project called LuaJIT that performs just-in-time compilation of Lua to native code. There's also MetaLua, which adds the feature of macros to the language. Better still, there's lua-Coat, which is a port of a subset of Moose from Perl (which is, in turn, a port of CLOS and other things to Perl) to Lua. Consider also just using Python or Io or any number of other languages. I guess my point is that it really doesn't depend on the language. If the environment isn't going to be extensible within reason, I probably won't use it. (Did you know that vim lacks the functionality to emulate Emacs' `create-frame`? That's a huge turn-off for me personally.)