Vi and Vim Stack Exchange is a question and answer site for people using the vi and Vim families of text editors. It only takes a minute to sign up.
Sign up to join this community
So my question is simple. Is it a good idea to learn vim scripting just to create vim or we should adopt some other more accepted languages to that.
For example This link opens a YouTube videos which shows How to use Python to create vim plugins.
Vim scripts are not entirely useful unless one intends to create some vim plugins. So is there any particular thing that can not be done unless vim scripts are used only ?
My plugins are 99% in VimL. The reason is that VimL is available where vim is installed. It's much more complicated with other languages -- for instance, it's rare I have Python installed on the windows boxes where I use Vim.
Of course VimL is cumbersome, it's missing many cool features, but at least, it's easier to have something portable.
The 1% not in VimL is when I need to interact with external API which offer python bindings.
BTW, almost everything you learn regarding VimL can be used interactively when you play with commands like :substitute. Most mappings or macros don't need python either.
map() that expects strings or (the unrelated) :map. I often have to play with/around string evaluation to come to my ends like generating mappings or processing list of function calls, ...
– Luc Hermitte
Nov 26 '15 at 12:34
execing snippets of VimL anyway. It lets you write your core logic in a language that you might be able to work a lot more efficiently in, but you still pretty much need to learn VimL.
– hobbs
Nov 27 '15 at 4:51
If you intend to write plugins you definitively should read the nice article "Writing Vim Plugins", by Steve Losh; not only for deciding if you will stick with VimL or not, but for the best practice advices.
It also contains a small discussion about Scripting Vim with Other Languages:
First, using another language will requires your plugin’s users to use a version of Vim compiled with support for that version. In this day and age it’s usually not a problem, but if you want your plugin to run everywhere then it’s not an option.
Using another language adds overhead. You need to not only learn Vimscript but also the interface between Vim and the language. For small plugins this can add more complexity to the project than it saves, but for larger plugins it can pay for itself. It’s up to you to decide whether it’s worth it.
Finally, using another language does not entirely insulate you from the eccentricities of Vimscript. You still need to learn how to do most things in Vimscript — using another language simply lets you wrap most of this up more neatly than you otherwise could.
My experience is that even when a non-VimL plugin is better, I end up switching to a pure VimL alternative later, mainly because of portability. Vim runs on virtually any system (even ugly and old legacy systems), and the overhead of setting up the dependencies or temporary disabling that plugin is not worth (especially if you keep forgetting that you disabled it and trying to use its mappings/commands).
Even when it is easier to setup the dependencies you can hit some problems (e.g.: some python-based plugins doesn't works 100% when they are sourced from shared folders on Virtual Machines). That is why the few plugins I wrote use VimL only.
