Wow, a lisp vs python vs vimscript thread and I almost missed it. > With languages like Vim > script there are two separate classes: commands and expressions
You also have keymaps and normal commands. But commands and normal commands could be seen as a DSL. The code often looks ugly and programming vimscript can get really messy, but it does the job well -- especially with the additions that were made in vim7. vim7's approach to prototype-based programming is neat. AFAIK emacs-lisp has no clean support for OOP. IIRC Sam Goldstein[1] recently proposed to write a clisp-interface for vim. With a full fledged common lisp environment under the hood, Emacs wouldn't stand a chance. Anyway, my only wish with regard to vim's scripting capabilities would be an improved ruby-interface that makes it possible to (from the script developer's perspective) directly access vim variables from ruby and vice versa without having to convert them to strings and back again. I think vim would gain much popularity by slightly improving those interfaces so that you could actually develop plugins in ruby/ python/perl/whatever without to much vimscript code around. [1] http://groups.google.com/group/vim_dev/browse_frm/thread/2212c1d7c3ad148a?hl=en# --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
