this?
===
#. ECL (Embeddable Common Lisp) Interface
Author: Mikael Jansson et al
Status: Mostly complete, needs testing
Site: http://common-lisp.net/project/limp
Implements many, but not all, of the VimScript functions. See the
project page for documentation.
===
Thanks
Mikael
John Beckett wrote:
Mikael Jansson wrote:
===
#. ECL (Embeddable Common Lisp) Interface
Author: Mikael Jansson et al
Status: Mostly complete, needs testing
Site: http://common-lisp.net/project/limp
Implements many, but not all, of the VimScript functions. See
the project
Hi,
The Limp team has prepared a patch for ECL-0.9L (Embeddable Common Lisp,
http://ecls.sourceforge.net) support, based on the work done by the
Slim-Vim project.
Applies cleanly against the official Vim-7.2 release, available at
http://common-lisp.net/project/limp/vim-ecl-7.2.diff.bz2
Tony Mechelynck wrote:
On 25/10/08 10:34, Mikael Jansson wrote:
Hi,
The Limp team has prepared a patch for ECL-0.9L (Embeddable Common Lisp,
http://ecls.sourceforge.net) support, based on the work done by the
Slim-Vim project.
Applies cleanly against the official Vim-7.2 release
, as anyone could add these types of features through
plugins. Same goes for IDE integration.
Right now, you have to write a proxy daemon translating your
application's native communication protocol to NetBeans. Sub-optimal.
Thoughts, comments?
- --
Mikael Jansson | http://mikael.jansson.be | GPG Key
Hi,
I have a patch against help.vim to enable proper syntax highlighting for
tags that are named like special variables in Lisp, i.e.:
*standard-output*
Corresponding tag would be called **standard-output**, which is
unfortunate as this will break highlighting. The attached patch fixes
Hi,
I've modified src/ex_cmds.c:helptags_one() to recognize tags that are
named like this:
**standard-output**
and have the tag
*standard-output*
be inserted into the tags file when using :helptags to generate
documentation.
See attached diff.
-- Mikael
(repost from vim_use, realized this is the better place)
Hi,
Vim seems to be able to use the remote-server functionality in src/
if_xcmdserv.c to process Vim code as it's received.
I'm considering using this for doing communication with outside
processes, and then be able to run Vim code
Ok, got it.
Note that I don't like the idea of running a shell in a Vim window. But
running make in the background would be useful.
Because this is on of the first steps from an editor to an operating
system
alla emacs ?
If someone starts a shell as a subprocess and redirect its in-
Esentially, I just want it to be enabled when I do filesystem completion
-- just like readline's completion-ignore-case. However, I can't make
much sense of os_unix.c / misc1.c. Could anyone help me by pointing me
in the right direction?
Thanks in advance,
Mikael
Maybe this is worth a
10 matches
Mail list logo