Can't use vcscommand.vim with Snow Leopard

[GoogleCodeExporter]

What steps will reproduce the problem?

Ran :VCSUpdate or other commands with MacVim GUI, the GUI will hang, and
perl10.5 process consume 100% of CPU usage(see sreenshot in attachment) 

Console messages filled with:

10/24/09 6:08:17 PM MacVim[391] -[MMVimController sendMessage:data:]@352:
processInput:data: failed: pid=396 id=1 msg=SetMouseShapeMsgID
reason=[NSPortCoder sendBeforeTime:sendReplyPort:] timed out
(278071697.436471 278071697.438507) 1

What version of MacVim and OS X are you using?

Snapshot 49, Snapshot 50, stable-1_2, 10.6.1 binary I built myself
Mac OS X 10.6.1

Please provide any additional information below.

built-in version of Vim work correctly

My vcscommand version is lastest 1.99.31:
http://www.vim.org/scripts/script.php?script_id=90

Original issue reported on code.google.com by dexter.yy on 24 Oct 2009 at 10:42

Attachments:

• [Screen shot 2009-10-24 at 6.09.13 PM.png](https://storage.googleapis.com/google-code-attachments/macvim/issue-227/comment-0/Screen shot 2009-10-24 at 6.09.13 PM.png)

[GoogleCodeExporter]

Could this be the same problem as Issue 216?

Original comment by bjorn.winckler@gmail.com on 24 Oct 2009 at 12:25

[GoogleCodeExporter]

I have tried the same as Issue 216 before i post this...but it seems different.

Original comment by dexter.yy on 24 Oct 2009 at 1:09

[GoogleCodeExporter]

You should contact the plugin author (I can't provide much help with debugging 
Vim scripts).

As far as I can tell the problem is not caused by MacVim but some interaction 
with Perl.  The messages you see in 
Console are logged because the Vim process stops responding (I'm guessing it's 
waiting for Perl to finish).  It is 
possible that this bug is reproducible in another GUI (but that it doesn't 
occur in non-GUI mode).

Original comment by bjorn.winckler@gmail.com on 24 Oct 2009 at 1:47

[GoogleCodeExporter]

The plugin doesn't invoke perl.  Do you have wrapper scripts around your vcs 
commands that use perl?

Original comment by bob.hies...@gmail.com on 24 Oct 2009 at 5:15

[GoogleCodeExporter]

I'm sorry, now you've lost me.  You wrote "... perl10.5 process consume 100%" 
so I assumed Perl was used by the 
script.  I've never tried vcscommand myself.

Did you manage to get in touch with the author?

Original comment by bjorn.winckler@gmail.com on 24 Oct 2009 at 6:24

[GoogleCodeExporter]

I was having some issues in svn repos where it was trying to use svk. I just 
removed
the svk part of the plugin, then it worked fine for me.

Original comment by cpar...@gmail.com on 29 Oct 2009 at 1:59

[GoogleCodeExporter]

I don't have the correct environment to duplicate this issue, but it sounds as 
though
the "svn info ." command that is executed as part of the VCS type identification
routine is hanging.

I recommend disabling the SVK part of the vcscommand plugin until the SVK issue 
is
resolved by putting some variant of the following in your vimrc:

let VCSCommandSVKExec='disabled no such executable'

Original comment by bob.hies...@gmail.com on 30 Oct 2009 at 6:49

[GoogleCodeExporter]

Thanks! Disabling the SVK is enough to fix my problem.

And As far as I know， SVK development is discontinued.
http://lists.bestpractical.com/pipermail/svk-users/2009-May/000425.html

Original comment by dexter.yy on 31 Oct 2009 at 1:48

[GoogleCodeExporter]

Original comment by bjorn.winckler@gmail.com on 28 Nov 2009 at 5:26

• Changed state: Invalid