[slim-vim] Slim-vim, future and milestones. (V0.1!!!)

[Brad Beveridge]

On 14/07/06, Larry Clapp <larry at theclapp.org> wrote:
> On Thu, Jul 13, 2006 at 03:37:32PM -0700, Brad Beveridge wrote:
> > On 13/07/06, Larry Clapp <larry at theclapp.org> wrote:
> > > On Thu, Jul 13, 2006 at 03:07:40PM -0700, Brad Beveridge wrote:
> > > > On 13/07/06, Larry Clapp <larry at theclapp.org> wrote:
> > > > > Are you using the latest vim70+async+ecl tree?  When I invoke
> > > > > the inspector (on a number, if it matters) I get an empty
> > > > > inspector window and a brief Vim error about "Using List as a
> > > > > String".
> > > > >
> > > > > -- Larry
> > > > >
> > > > > _______________________________________________
> > > > > slim-vim mailing list
> > > > > slim-vim at lispniks.com
> > > > > http://www.lispniks.com/mailman/listinfo/slim-vim
> > >
> > > Just by the way, to you and everybody on the list, please cut the
> > > header from your reply.  VGx should do it in most cases.  :)
> > >
> > > > No, I'm not actually using the latest vim repo, though I don't
> > > > think that I am _that_ far out of date.  I'll do a pull tonight
> > > > and fix the bug (unless you feel like fixing it first!).  I'm
> > > > guessing that get-line might return a string in my slightly
> > > > older version?
> > >
> > > I just meant the Vim7 version as opposed to the old Vim6.4
> > > version.
> > >
> > > I found the problem, but haven't fixed it yet.  In
> > > buffer-util.lisp you (vim:funcall "tabpagebuflist"), which gives
> > > the "Using List as a String" error.  :echo tabpagebuflist() prints
> > > "[1, 4]" (without the quotes) which is apparently not a string.
> > > It appears to be a fundamental problem with vim:funcall'ing a Vim
> > > function that returns a List.
> >
> > Which header do you mean?  The three lines that are appended at the
> > end by the mailing list program?
>
> Yeah, I should have said "trailer".  When one person doesn't do it,
> it's no big deal, but it bugs me to see
>
>   > > > <four-line-trailer>
>   > > <four-line-trailer>
>   > <four-line-trailer>
>   <four-line-trailer>
>
> in a thread, so I wanted to take a moment to encourage everyone on the
> list to cut it out of the messages they reply to.
>
> > I remember this bug now - the issue is in Vim7.  It if_ecl.c there
> > is a call to eval_to_string, which calls into Vim's eval.c module.
> > If you look at eval_to_string, you can either get back a Vim List
> > (which at the moment our FFI can't parse), or a string that uses \n
> > as an item seperator.  I changed if_ecl.c to output the later.  I
> > don't have the code in front of me as a complete unit, so I can't
> > really be more specific, sorry.
>
> I found it.  I'd like to make it return a Lisp list.
>
> > Hope that helps.  If it does, can you please check the change in to
> > the Vim7 repo?
>
> I will when I make them.  :)

I'd also prefer a list, but at the time I was in a bit of a hurry.
Can you please still check the current "fix" in so that anybody
getting from the Vim7 repo won't see this bug?  When it returns a list
proper I'll fix my stuff up.
Also, now that we use the tabpagebuflist command we are no longer
vim6.4 compatible.

Cheers
Brad


-- 
Go and see "An Inconvenient Truth"
http://www.climatecrisis.net/