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

[Brian Kalbfus]

A pre-compiled Win32 executable would allow me to start using this.  I'm 
stuck with Windows right now.  compiling under cygwin has been 
troublesome (currently I make everything and vim just exits immediately 
upon opening).

Thanks,
Brian

Brad Beveridge wrote:
> On 06/07/06, Brad Beveridge <brad.beveridge at gmail.com> wrote:
>   
>> On 06/07/06, Larry Clapp <larry at theclapp.org> wrote:
>>     
>>> On Thu, Jul 06, 2006 at 03:42:29PM -0700, Brad Beveridge wrote:
>>>       
>>>> I am slowly getting work done on Slim-Vim.  I didn't get as much
>>>> done over the long weekend as I would like, but I'm trying.
>>>>         
>>> You're doing great work, Brad.  Work has sucked or I'd have been able
>>> to play with slim-vim more, or even help out.  Thanks for keeping at
>>> it!
>>>
>>>       
>> Thanks for the encouragement Larry, much appreciated :)
>>
>> Brad
>>
>>     
> 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
>
> Cheers
> Brad
>
>