Hello, all, As you may know, I wrote VILisp, a (very) poor knock-off of ILisp (then-reigning champion of Emacs->Lisp interaction, since (mostly) supplanted by SLIME).
How may of you use Vim and just drool at the thought of SLIME for Vim? I thought it'd be easier to just use Emacs than write a SLIME plugin for Vim, but if lots and lots of people want it, maybe it wouldn't be so pointless after all. My mode of attack would probably be something like: a) Perl module to talk to Swank, the SLIME backend that runs on the client Lisp. (Vim-script is too primitive to copy slime.el directly. For example, it has no networking.) b) Vim interface to the Perl module. This would mean that whatever Vim you used would have to have Perl compiled in. The precompiled Vim for Windows has Perl builtin, and you can get Vim+Perl for Debian easily, too. It would also mean a stand-alone way to remote-control a remote Lisp, debugger and all, which wouldn't suck. :) -- Larry _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
