search

ramccor / vcscommand

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

After installing vcscommand, exiting vim returns nonzero error code to shell #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install vcscommand 
2. Launch vim and edit a file
3. Shift-ZZ to write file and quit

What is the expected output? What do you see instead?
Expected: vim should exit back to shell with return code of 0
Actual: vim returns nonzero exit code

What version of the product are you using? On what operating system?
vcscommand Beta 19
Mac OS X Leopard 10.5.1 on x86
vim 7.0.234

Please provide any additional information below.
The nonzero return code causes svn commits to fail with the following message:
svn: Commit failed (details follow):
svn: system('vim svn-commit.tmp') returned 256

Original issue reported on code.google.com by pch...@gmail.com on 19 Dec 2007 at 3:07

GoogleCodeExporter commented 9 years ago 
Unable to duplicate so far, whether using for SVN editor or not.

Original comment by bob.hies...@gmail.com on 2 Feb 2008 at 12:28

GoogleCodeExporter commented 9 years ago 
Still seeing the problem with vcscommand Beta 20.  

Through some trial and error, I found that commenting out the following line on 
line 424 of vcscvs.vim 
eliminates the problem:
    silent! aunmenu Plugin.VCS.CVS

Original comment by pch...@gmail.com on 7 Feb 2008 at 7:02

GoogleCodeExporter commented 9 years ago

Original comment by bob.hies...@gmail.com on 11 Mar 2008 at 11:23

GoogleCodeExporter commented 9 years ago 
I still cannot replicate this, using only the vcscommand and vcscvs plugins.

I suspect that it is either a bug in your vim (I'm running 7.1.283) or 
interaction
with another plugin.  Can you disable all other plugins and manually vcscvs in 
the
commit message session?

Original comment by bob.hies...@gmail.com on 19 Mar 2008 at 6:53

GoogleCodeExporter commented 9 years ago 
After updating to 7.1.285, the problem no longer occurs.  So I think this issue 
is OK to close.

Original comment by pch...@gmail.com on 31 Mar 2008 at 8:10

GoogleCodeExporter commented 9 years ago 
Thanks for the update.

Original comment by bob.hies...@gmail.com on 31 Mar 2008 at 12:34