[Ecls-list] Problems with ECL in vim

[Larry Clapp]

On Mon, Apr 03, 2006 at 09:43:38PM +0200, Daniel Trstenjak wrote:
> there is a project which tries to make vim a better lisp development
> platform (http://wiki.alu.org:80/Perl_interface_to_SLIME).

See also http://wiki.alu.org:80/Vim_ECL for a description and
http://wiki.alu.org:80/Slim-Vim-Repos for links to code.

In particular, see
http://theclapp.org/repos/vim+async+ecl/src/if_ecl.c for the ECL
interface code for Vim.  It's pretty straightforward C.

> One thing they have alreay done is embedding ECL in vim.
> It seems to work for all project members. 
> Unfortunately it does not work for me, and nobody of the project has
> a clue why.
> 
> When I try to call ECL from vim I always get an abort from ECL with
> the message:
> 
> "Unrecoverable error:
>  Lisp initialization error."
> 
> Here is the backtrace when calling (print "ok"):
> 
> #0  0xffffe410 in ?? ()
> #1  0xbfffe5b8 in ?? ()
> #2  0x00000006 in ?? ()
> #3  0x00007c70 in ?? ()
> #4  0x406a42c1 in raise () from /lib/tls/libc.so.6
> #5  0x406a5b75 in abort () from /lib/tls/libc.so.6
> #6  0x405f02e5 in error (s=0x4063c795 "\nLisp initialization error.\n") at error.d:48
> #7  0x405f0328 in universal_error_handler (narg=3, c=0x81961a0, err=0x819b300, args=0x83b0f80) at error.d:221
> #8  0x4060df97 in APPLY (n=3, fn=0x405f02f0 <universal_error_handler>, x=0x833b014) at apply.d:26
> #9  0x405d8122 in cl_funcall (narg=3, function=0x819cc38) at eval.d:219
> #10 0x405eff17 in cl_error (narg=5, eformat=0x819b300) at error.d:294
> #11 0x405f0126 in FEwrong_type_argument (type=0x819a358, value=0x8335100) at error.d:151
> #12 0x405f2ee8 in FEtype_error_real (x=0x8335100) at typespec.d:36
> #13 0x405f4d6e in make_complex (r=0x8335100, i=0x83a2480) at number.d:231
> #14 0x405eb3dc in sharp_C_reader (in=0x8303910, c=0x10e, d=0x81961a0) at read.d:679
> #15 0x4060f78b in APPLY_fixed (n=3, fn=0x405eb2c0 <sharp_C_reader>, x=0x833b008) at apply.d:677
> #16 0x405d80b1 in cl_funcall (narg=3, function=0x8333b28) at eval.d:216
> #17 0x405e7ebe in dispatch_reader_fun (in=0x8303910, dc=0x8e) at read.d:617
> #18 0x4060f78b in APPLY_fixed (n=2, fn=0x405e7df0 <dispatch_reader_fun>, x=0x833b000) at apply.d:677
> #19 0x405d80b1 in cl_funcall (narg=2, function=0x8333c00) at eval.d:216
> #20 0x405e986a in read_object_with_delimiter (in=0x8303910, delimiter=-1) at read.d:123
> #21 0x405ea970 in read_VV (block=0x830cbd0, entry_point=0x4057f687 <init_ECL_NUMLIB>) at read.d:2001
> #22 0x4055f079 in init_LSP (cblock=0x1) at /home/dan.t/downloads/ecls/build/ECLINITQI7Y8c.c:98
> #23 0x405ea8cb in read_VV (block=0x830cfc0, entry_point=0x4055eef0 <init_LSP>) at read.d:2023
> #24 0x4055e77b in cl_boot (argc=0, argv=0x6) at main.d:451

Above this is ECL code; below this is Vim code ...

> #25 0x08160e0e in RunEclCommand (eap=0xbfffec10, cmd=0x81be6bc "(print \"ok\")") at if_ecl.c:478
> #26 0x08161144 in ex_ecl (eap=0xbfffec10) at if_ecl.c:564
> #27 0x0808b42c in do_one_cmd (cmdlinep=0xbfffefa8, sourcing=0, cstack=0xbfffed80, 
>     getline=0x809b180 <getexline>, cookie=0x0) at ex_docmd.c:2475
> #28 0x080891b8 in do_cmdline (cmdline=0x0, getline=0x809b180 <getexline>, cookie=0x0, flags=0)
>     at ex_docmd.c:991
> #29 0x080ecc16 in nv_colon (cap=0xbffff070) at normal.c:4764
> #30 0x080e70e6 in normal_cmd (oap=0xbffff0e0, toplevel=1) at normal.c:1116
> #31 0x080b9bb2 in main_loop (cmdwin=0) at main.c:2183
> #32 0x080b984d in main (argc=0, argv=0xbffff328) at main.c:2001
> 
> ECL alone works well. So the problem seems to be in conjunction with vim.
> Has anybody an idea what the problem could be ?
> I appreciate every answer.

-- Larry