gvim hangs if svn asks for user input

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Check out a Subversion repository
2. Somehow lose the login cache (checkout with --no-auth-cache for example)
3. Try and run a VCS command against the server (Update, Commit, etc)

What is the expected output? What do you see instead?
Command should "do something". In fact it hangs and gvim has to be killed.

What version of the product are you using? On what operating system?
beta-22, Linux, gvim only. It works as expected with regular terminal vim,
and you can input the password as expected. Also seen on Windows - spotted
on the vim_use list here though version unknown:
http://groups.google.com/group/vim_use/browse_thread/thread/dc29f1652b23b817

Please provide any additional information below.
Perhaps with svn you could use the "--non-interactive" flag with gvim so at
least if there are no log in details cached it would bomb out immediately
instead of hanging.

Original issue reported on code.google.com by richard.quirk on 2 May 2008 at 10:22

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Interestingly, it doesn't work for me in
console version when I blow away the cached info from my home
directory.  I think always using '--non-interactive' as you suggest is
the appropriate solution.  Thoughts?

Original comment by bob.hies...@gmail.com on 2 May 2008 at 4:34

[GoogleCodeExporter]

Hmm, that's strange. My test was to delete just the 
~/.subversion/auth/0123456...
that corresponded to the test svn:// server I set up, if that makes any 
difference.

I wouldn't worry too much about it... on Linux at least svn is very keen on 
caching
the user's password, so you have to go to some lengths not to do it. On Windows 
it
sounds like it gets cached in %TMP% (or whatever) and gets blown away on a 
reboot.
The workaround's pretty painless if --non-interactive prevents hangs.

My only doubt would be how far back --non-interactive goes in subversion's 
history.
If it's been there since day 1, no problem, but if it's a newish option it might
cause compatibility problems for users running older clients.

Software... isn't it wonderfully simple? ;-)

Original comment by richard.quirk on 2 May 2008 at 6:16

[GoogleCodeExporter]

This fix at least brokes `svn add', so adding --non-interactive option to svn 
command
line permanently wouldn't be a solution.

Original comment by anton.mi...@gmail.com on 3 May 2008 at 11:03

[GoogleCodeExporter]

Ouch, thanks.  I've removed beta23 while I figure out how I want to do this.

Original comment by bob.hies...@gmail.com on 5 May 2008 at 1:16

[GoogleCodeExporter]

At least for now I'm taking the easy route and simply specifying 
'--non-interactive'
on those commands which support it.  Please take a look at 1ba7979.  This will 
be
released at the next public release.

Original comment by bob.hies...@gmail.com on 16 Sep 2008 at 8:55

• Changed state: Fixed

[GoogleCodeExporter]

Please note, I still can't replicate this issue in my environment, so I can't 
be sure
that it works without others' help testing.

Original comment by bob.hies...@gmail.com on 16 Sep 2008 at 9:05