Re: visual_studio.vim

>> Yes, I thought the allowance for calling an external Python was
>> superfluous, since both the official and Cream's build of Vim are
>> built with Python support. It just added an unnecessary complexity.
>
> Henrik,
>
> Upon trying out your version of visual_studio.py and
> visual_studio.vim, I got some errors in the log_func() calls,
> specifically:
>
>    AttributeError: 'tuple' object has no attribute 'args'  (line 790)
>
> I believe this is because you are relying on Python 2.6 functionality,
> while I am using Python 2.5; does that seem accurate? It's a very easy
> fix to make it work with 2.5 of course, just be explicit with the
> return tuple from getargvalues(), thus:
>
>    args,varargs,varkw,locals = inspect.getargvalues(frame[0])
>
> And of course, fix the corresponding uses of arg_info.
>
> Other than that the script works great; I have my asynchronous version
> working already and I'll share it soon.

Actually, Henrick, it seems like there are a multitude of bugs in your
branch of the script; build_solution and build_project both start
throwing errors. It could be that it just supports Python 2.6, but it
shouldn't be difficult to make it backwards compatible with Python
2.5.

My async stuff works great, although sadly it currently only works
with compile_file, as the other two are blocked from working because
of the errors. If you'd like more information on what is failing let
me know; it might be best to take this discussion off the vim mailing
list though.

Max

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