fourjay / vcscommand

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

SVN 1.7.x diff and annotate no longer working #93

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open revision controlled file with modifications into vim
2. Run vimdiff (\cv) or annotate (\cn)
3. Nothing happens, and no error message.

What is the expected output? What do you see instead?
\cv "thinks" for a few seconds, then returns nothing. But \cd shows correct 
diff. Only noticeable change is a 2 char wide grey bar on the left edge of 
screen, but no new buffer is created to show the diffsplit. (And :vert 
diffsplit is working in this VIM).

\cn (annotate) thinks for a few seconds, then does nothing. No noticeable 
change to editor window.

Strangely, the following commands all work correctly:
\cd, \cl, \ci, \cs, \cL, \cU, \cq, \cc, \cc and \cu

All worked fine with subversion 1.6.17 and a previous version of vcscommand.

What version of the product are you using? On what operating system?
Subversion 1.7.3, vim 7.3, RHEL4/5 32-bit. vcscommand upgraded to v1.99.46 to 
get basic functionality back with Subversion 1.7 (missing .svn directory 
problem with older vcscommand).

Please provide any additional information below.

Original issue reported on code.google.com by davros...@gmail.com on 28 Feb 2012 at 8:31

GoogleCodeExporter commented 8 years ago
I am getting No Suitable plugin errors again, and I determined the following:
:VCSDiff and :VCSVimDiff always work correctly from command line vim. The 
problem occurs when I run "vim -rv -g" or "gvim".
Oddly, some working copies work fine with gvim, and vim -rv -g. When it does 
not work, :VCSDiff sometimes returns "No differences found", where svn diff 
does show differences, and so does :VCSDiff if not using gvim.
Any idea why the GVim environment (or vim -rv -g) could cause vcscommand to 
break when it otherwise works with command-line vim?

Original comment by davros...@gmail.com on 11 Mar 2012 at 9:59

GoogleCodeExporter commented 8 years ago
Problem found and solved. I believe this problem was only happening on files 
with embedded copyright symbols (circle-C character). When I changed my LANG 
variable from en_US to en_US.UTF-8, that fixed VCSDiff commands from within 
GVIM.

Very strange since en_US has worked for me for years with same VIM and same 
VCScommand. Only recent change was SVN 1.6.17 -> 1.7.3 upgrade, and svn diff 
command line operates just fine with LANG=en_US.

Please remove as an issue.

Original comment by davros...@gmail.com on 11 Mar 2012 at 10:17

GoogleCodeExporter commented 8 years ago
Removing per requestor.

Original comment by bob.hies...@gmail.com on 21 Mar 2012 at 1:45