Re: visual_studio.vim

Upon a quick skim, it seems like you have removed support for using
external Python, and rely on vim's built in Python; is that accurate?

My async version requires external Python, for obvious reasons, unless
you can suggest an alternative?

Cheers,

Max

On Mon, Jan 25, 2010 at 9:37 AM, Henrik Öhman <speeph@gmail.com> wrote:
> On Jan 25, 3:53 pm, Max Dyckhoff <max.dyckh...@gmail.com> wrote:
>> That's what I'm doing! :)
>
> :)
>
>> I'm actually in the process of writing (whenever my project is
>> compiling) an asynchronous version of visual_studio.vim that can be
>> turned on with a global. It's great so far, I just need a few more
>> hours to finalize everything. Is the author (Michael Graz) still
>> around, and would anyone else be interested in seeing my async
>> version?
>>
>> Max
>
> He has responded to email in the past.
>
> I've forked the project, because I wanted to implement some
> functionality of my own, and felt like I wanted to rewrite most of it
> to get a better separation of Vim and Python code. Feel free to use it
> if you like - it's fairly well tested, but some bugs are still there.
> You can find it at http://github.com/spiiph/visual_studio.
>
> Regards,
> Henrik
>
> --
> You received this message from the "vim_use" maillist.
> For more information, visit http://www.vim.org/maillist.php

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php