search

ramccor / vcscommand

Automatically exported from code.google.com/p/vcscommand
0 stars 0 forks source link

version control command failed: svn command not found #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. open a file in gvim (file under svn version control)
2. call vcslog command in gvim
3. error: VCSCommand: Version control command failed: svn: Command not found

What is the expected output? What do you see instead?
-> svn log of the file

What version of the product are you using? On what operating system?
GVIM 7.2, SunOs

Please provide any additional information below.

Original issue reported on code.google.com by bsandee...@gmail.com on 2 Feb 2010 at 7:54

GoogleCodeExporter commented 9 years ago 
Have you set any VCSCommand<Blah> options?

Original comment by bob.hies...@gmail.com on 2 Feb 2010 at 4:24

GoogleCodeExporter commented 9 years ago 
No options set, I just copied all the files in plugin directory.
And tried to execute "vcslog" command in gvim.

we are using both cvs and svn for version control for different database.
same command works for files under cvs version control :)
Do I have to do anythind special here?

Original comment by bsandee...@gmail.com on 2 Feb 2010 at 6:14

GoogleCodeExporter commented 9 years ago 
I have the same issue with VCSCommit and svn. If I set the VCSCommandSVNExec to 
the 
full path of svn client, I get error in the second attachment. I also tried svn 
client 
path with and without space.

Original comment by schnel...@gmail.com on 22 Feb 2010 at 8:40

Attachments:

GoogleCodeExporter commented 9 years ago 
For schnell18, what OS are you using?  Does *only* commit fail?  If the answers 
are 
'Windows' and 'yes', please try v1.99.39 of the script and let me know if that 
fixes 
it.

Original comment by bob.hies...@gmail.com on 29 Mar 2010 at 7:48

GoogleCodeExporter commented 9 years ago 
For bsandeep04, which version of the plugin are you using?

Did this work previously and stop working when you switched plugin version?

What are the paths to your cvs and svn executables?

I'm attaching a version of vcscommand.vim that displays the full command line.  
If 
you don't mind, please use this version and, after running the command that 
fails, 
type:

:messages

and then copy and paste the line that looks like this:

VCSCommand DEBUG:  about to execute:  'git' log -- "vcscommand.vim"

Original comment by bob.hies...@gmail.com on 29 Mar 2010 at 8:02

Attachments:

GoogleCodeExporter commented 9 years ago 
I encountered with similar problem, It seems to because it attached an 
redundant 
quotation mark( '') surround 'svn'. But I do not know how to remove it? 
Is there anybody know how to remove it or fix the bug ? Thanks for your 
selfless 
contribution to this plugin.

Original comment by tanli...@gmail.com on 11 May 2010 at 7:13

Attachments:

GoogleCodeExporter commented 9 years ago 
tanliboy:  the image is truncated for me.  What version of the plugin are you 
using?  
If you're not using 39 or above, could you please install at least 39 and see 
if it 
fixes the issue for you?

Original comment by bob.hies...@gmail.com on 17 May 2010 at 1:09

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I have encountered the same problems.

I am using latest vcscommand version and Gvim 7.2 on windows xp pro. And I am 
using
recent SVN.
I ran the :messages and it says

VCSCommand DEBUG: about to execute: 'svn' status --non-interactive -- "file.m"
VCSCommand: Version Control command failed: ''svn'' is not recognized as an 
internal
or external command, operable probram or batch file.

Original comment by juch...@gmail.com on 3 Jun 2010 at 2:33

GoogleCodeExporter commented 9 years ago 
I get this issue when attempting to run any SVN command. I'm using Windows XP. 
I have
both TortoiseSVN and a command-line SVN implementation installed (SlikSVN). The 
svn
executable is in my $PATH environment variable. I'm really not sure how to set 
the
VCSCommandSVNExec option... I took a stab at adding either of the following:

let VCSCommandSVNExec = "c:/Program\ Files/SlikSVN/bin/svn.exe"

or

set VCSCommandSVNExec="c:/Program\ Files/SlikSVN/bin/svn.exe"

to $VIM/_vimrc (not at the same time) and restarting gVim but to no avail.

Any help/advice you can give would be appreciated. I'm using 1.99.40 of 
vcscommand.
Thanks in advance and let me know if I need to provide any further information.

-Michael

Original comment by michael....@gmail.com on 3 Jun 2010 at 3:10

GoogleCodeExporter commented 9 years ago 
Michael,

you can try this before set the variable, VCSCommandSVNExec.

verbose set sxq=\"

But, it will generate error message like "no suitable plugin"

Original comment by juch...@gmail.com on 3 Jun 2010 at 3:24

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Thanks for the tip juchirl... I tried your suggestion, restarted gVim, opened a 
file
that I knew had diffs from HEAD, hit \cv and got

"VCSCommand: Version control command failed: ''svn'' is not recognized as an 
internal
or external command, operable program or batch file.
Can't open current revision.
Press Enter or type command to continue."

So... back to square one. :(

Original comment by michael....@gmail.com on 3 Jun 2010 at 6:35

GoogleCodeExporter commented 9 years ago 
Michael,

You need to write with any space I assume like

verbose set sxq=\"
let VCSCommandSVNExec="c:\Program Fiels\SlikSVN\bin\svn.exe"

but it doesn't solve the problem entirely.

Too bad.

Original comment by juch...@gmail.com on 4 Jun 2010 at 1:20

GoogleCodeExporter commented 9 years ago 
juchirl,

  What do you see if you try to execute svn directly from within VIM?

:!svn info

bob

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 1:53

GoogleCodeExporter commented 9 years ago 
Michael,

  You shouldn't need to escape any spaces at all.  Use forward slashes in your string, 
so something like this:

let VCSCommandSVNExec = "c:/Program Files/SlikSVN/bin/svn.exe"

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 1:55

GoogleCodeExporter commented 9 years ago 
Bob,

It works fine.

Original comment by juch...@gmail.com on 4 Jun 2010 at 1:59

GoogleCodeExporter commented 9 years ago 
Michael,

  Did you try this before setting the exec prefix variable?  Have you been successful 
with any other VCS?

bob

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 2:11

GoogleCodeExporter commented 9 years ago 
juchirl,

  Do you have shellslash set?  If so, can you please disable it and try again?  You 
shouldn't end up with:

  'svn'

It should be:

  "svn"

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 2:22

GoogleCodeExporter commented 9 years ago 
I left out some important information, it seems. Normally I run Linux Mint and 
have
absolutely no issues with this plugin whatsoever (it's a "must have plugin" for 
me,
btw, so massive kudos to you, Bob, for your work! :).

I recently moved to a new job and they've given me a WinXP box. Ugh. I'm trying 
to
get up and running with gVim on WinXP. Not being familiar with how gVim is set 
up on
Windows, I decided to install Cream instead of the standard windows gVim 
install.

It seems that cream-conf.vim and cream-user.vim are run after $VIM/_vimrc. So, 
I put

set noshellslash
let VCSCommandSVNExec = "c:/Program Files/SlikSVN/bin/svn.exe"

in my cream-user.vim, since that one is evaluated last.

Now, what happens when I use <Leader>cv is that a cmd window opens (expected) 
svn is
run and gVim (cream) goes into diffmode with the correct data in the buffer (I 
made
sure to use a working copy that had changes in it).

When I closed the diff buffer, though, vim remained in diffmode. So I hit 
:diffoff to
get it out then hit <Leader>cv again to see what would happen. This time, gVim 
went
into diffmode, but the buffers showed no differences. Again, hitting :q did not 
end
diffmode. I've never had this issue in vim before. Here I'm thinking it's either
Cream or just WinXP, but I'm not sure.

Very curious. Pending other advice that could help, perhaps Monday I'll try
uninstalling Cream, installing the official gVim distribution, and configuring 
that
to my liking.

Original comment by michael....@gmail.com on 4 Jun 2010 at 4:28

GoogleCodeExporter commented 9 years ago 
It works beautifully.

Thanks.

Juchirl.

Original comment by juch...@gmail.com on 4 Jun 2010 at 5:20

GoogleCodeExporter commented 9 years ago 
Is shellslash set by Cream by default?

Michael, I don't have any other advice to offer, though at least it sounds like 
things are mostly working.  The vimdiff code is a little tricky, and it's 
certainly 
possible there are bugs there, particularly if you have other code that manages 
buffers or acts when buffers are removed.  I rely on autocommands to clean up 
diffmode, which is easily broken by other plugins.

I'd also recommend using cygwin in your situation, as it generally makes life 
easier 
for people who are reluctantly stuck with Windows (like me).

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 8:32

GoogleCodeExporter commented 9 years ago 
I'm going to mark this closed if I don't hear anything else on the issue.  It 
seems to 
me that setting shellslash is a mistake on a windows installation, but if there 
are 
good uses for that, I may be able to work around it.

Original comment by bob.hies...@gmail.com on 4 Jun 2010 at 8:33

GoogleCodeExporter commented 9 years ago 
Closing this for now.  If any of you still have issues, please let me know.

Original comment by bob.hies...@gmail.com on 22 Aug 2010 at 10:53

GoogleCodeExporter commented 9 years ago 
I just upgraded to Windows 7 running 64-bit Vim (using 
http://code.google.com/p/vim-win3264/) and I'm seeing the "''svn'' is not 
recognized as an internal or external command, operable program or batch file." 
error message.  I disabled 'shellslash' and that worked for VCSCommand, however 
it broke other features.  For instance, if I have grep matches (or pyflakes 
messages, etc.) in a location list, each time I click on an item in the 
location list a *new* file is opened, even if a buffer containing that file 
already exists (active or hidden).  While these other issues aren't your 
problem, are there any other suggestions to fixing the original issue?

Thanks,
Troy

Original comment by troy.zim...@gmail.com on 29 Sep 2010 at 7:55

GoogleCodeExporter commented 9 years ago 
Please disregard my comment.  My issue is related to having MKS toolkit 
installed which changed the 'shell' Vim was using.

Original comment by troy.zim...@gmail.com on 30 Sep 2010 at 2:05

GoogleCodeExporter commented 9 years ago 
Hey FYI, I ran into this same problem on Win7 64-bit with version 1.99.47 on 
gVim 7.3. I diffed this with version 1.99.46 and reverted the change in 
"function! s:VCSCommandUtility.system(...)" (in vcscommand.vim), and _viola_, 
it works for me now.

Wonderful script, BTW. "VCSBlame!" alone is life-changing. :D Is there a way to 
show the revision log message as well?

Original comment by fisher....@gmail.com on 21 Mar 2014 at 3:35

GoogleCodeExporter commented 9 years ago 
Nevermind. Just found "VCSLog <revision number>". That's good enough for me. 
Thanks!

Original comment by fisher....@gmail.com on 21 Mar 2014 at 3:38