[slim-vim] Critical features before you'd use Slim-vim

[Brad Beveridge]

On 17/07/06, Larry Clapp <larry at theclapp.org> wrote:
> On Sun, Jul 16, 2006 at 09:47:04PM -0700, Brad Beveridge wrote:
> > This is my current priority list.  I'm pretty flexible about it, so
> > if there is something on there that you want more, let me know and
> > I'll promote it.
> >
> >  - compile file, compile and load file, compile defun
> >  - send interrupt
> >  - change the debug output to be more inline with the Slime messages buffer
> >  - macro expanding, insert arglist?
> >  - inspector describe
> >  - compiler note handling
> >  - profiling - debugger improvements, restarting, stepping, breaking,
> > interactive evals
> >  - documentation support - edit-definition (of the current symbol)
> >  - complete symbol?
> >  - who calls, who references, who binds, who sets, etc
> >  - support *use-dedicated-output-stream* == NIL
>
> I haven't used it tons, so this is just a guess, but I'd say put
> complete symbol below send interrupt.  I really like Vim's symbol
> completion; I suspect Slime's would come in similarly handy.
>
> If I have time (no promises :) I'll look into it myself.
>
> -- L
>
The reason I put completion further down the list is
1) I find Vim's autocomplete to be pretty good already (though,
Slime's could be fantastic and I just don't know what I am missing)
2) Ideally we'd build it into Vim's new omni-complete (^X^N)

Though I gotta say that I don't like having to hit ^X before ^N to get
at the omnicomplete functionalty.

Cheers
Brad

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