[slim-vim] Starting: problems in process-available-input

[Tomas Zellerin]

On 8/16/06, Brad Beveridge <brad.beveridge at gmail.com> wrote:
> On 16/08/06, Tomas Zellerin <zellerin at gmail.com> wrote:
> > On 8/16/06, Tomas Zellerin <zellerin at gmail.com> wrote:
> > > - A vim function has() should accept "ecl" as argument and then return
> > > 1 when it is present (it returns not for me, thought +ecl is in
> > > features), and it should be used to guard the new features dependend
> > > on ecl presence. *
> >
> > Sorry to reply to myself, but see attached trivial patch. (oh, I see
> > it should be also fixed in eval.txt help file...)
> > Tomas
> >
> Thanks Tomas!  Great stuff, and we'd love to see more patches :)  If
> you could create the patches using darcs record/darcs send
> (http://abridgegame.org/darcs/manual/), then it is trivial for us to
> apply the patch to the main repo.  I prefer this method because then
> you the patch author can write a changelog entry that stays with the
> patch.
>
Hmm, I can look at it, but the problem is that the machine I usually
work on things like this has never been online, and this is to stay
that way for some time. And yes, I dont know darcs, but this can be
fixed easily :)

Also, some of the other questions react more on current usage mode - I
think that using of the slim-vim should require only starting vim
(without any environment variables - script can do it, let $VAR =
value, and for location of the scripts would be possibly better a vim
variable anyway) and pressing correct key combination to do the rest
(load the heavy machinery, possibly even start the external lisp
program, and connect). Details - where is the ecl-slime, what lisp to
start - should be stored in lisp variables that have reasonable
default and can be modified e.g. in users vimrc file. This is what I
would want as a user. However, I wont make and send this as patch at
least now, because (a) this would be major overhaul of the system that
I wont go into it without consultation of authors and (b) it could
break any outstanding patches on the way.

Another design question - what is relation between ecl-repl and
ecl-slime? Does the latter require the former or not? If I understand
correctly, they both do the same thing on different lisp, and that was
a bit confusing to me at first. Is there a reason why to use slime one
would want to have ecl-repl at hand too?

Regards,

Tomas