|Don't ask to ask, just ask|
Environments extended with embeded Perl: are they for real?by stefp (Vicar)
|on Mar 23, 2003 at 22:41 UTC||Need Help??|
I just tried two environments (vim and emacs) extended with Perl and felt flat on my face. Clearly these extensions are not maintained/used. Why?
Side note: See below for a more detail story about my exeriences with emacs and vim Perl extensions
In these two cases, the explanation may be simple. Elisp is the accepted extension emacs language . Vim also comes with its own extension language even if it supports many other extension languages. Also you can do a lot by selecting a region and running it thru Perl so Perl as an extension language is unnecessary but for the more ambitious undertakings.
This led me to general thoughts about Perl as an extension language:
I switched a long time ago (circa 90) to emacs from vi because I could do everything in one emacs session (besides editing various files in different buffers, having different shell sessions, debugging using perldb or gdb...) but I always sincerely hate lisp syntax so I dislike very much to have to mess with emacs configuration files. Another PITA: emacs has been extended by so many people with extension following different conventions
I decided to look back at vi; or more precisely to its vim avatar. Except for the lack a of a decent pager and the ability to run shell or debugger. It seems pretty nifty.
Better, it supports many extensions languages including Perl. It is documented right in the nice hyperlinked system. So I tried it:
: perl $main::curwinThis is supposed to access the variable for the current window. I got a segmentation fault.