bug: Useless error message when SVN_SSH points to non-existent file

This is svn 0.23.0 on Cygwin, configured with
"--prefix=/usr/local/stow/svn-0.23.0"

Since this is a client-only installation, I don't have Berkeley DB
installed.

Here's an example of subversion working happily:

        $ svn ls svn+ssh://offby1.atm01.sea.blarg.net/home/offby1/svn-repos/trunk/config-files

When I run this, I see, as I expect, a list of the files in my
`config-files' directory on the repository.

(Of course if *you* try exactly the above, it'll fail because you
can't log in to that machine. But you get the point.)

Now here's how to reproduce the problem that I'm whining about:

        $ SVN_SSH=garbage svn ls svn+ssh://offby1.atm01.sea.blarg.net/home/offby1/svn-repos/trunk/config-files

In this case, instead of seeing an error message to the effect of "I
can't run the SSH program `garbage' because command not found", I see

        svn: Network connection closed unexpectedly
        svn: Connection closed unexpectedly

This actually bit me -- I had set SVN_SSH in my environment while
playing with some Win32 subversion clients, and then forgot that it
was there. Afterwards, every time I tried to run the Cygwin
subversion, I got the above cryptic message, and had to scratch my
head for a long time before I figured out what was wrong.

-- 
Tobacco: It's not just for killing children anymore.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org