[issue1263] ssh argument doesn't accept file names containing spaces on Windows

[David Adam]

New submission from David Adam <zanchey at ucc.gu.uwa.edu.au>:

hg's -e/--ssh argument gets confused if you try and pass a file name containing
spaces as the SSH command on Windows, although long file names without spaces work.

This occurs even when the filename is surrounded by quotation marks, which is
the standard way of protecting long file names on Windows.

As follows:

--8<--

; Acceptable - unprotected spaces in file name
D:\src\1>hg pull -e C:\Program Files\PuTTY\plink.exe
abort: repository Files\PuTTY\plink.exe not found!

; With spaces protected
D:\src\1>hg pull -e "C:\Program Files\PuTTY\plink.exe"
remote: 'C:\Program' is not recognized as an internal or external command,
remote: operable program or batch file.
abort: no suitable response from remote hg!

--8<--

This can be worked around by using old-style compatibility names - in this case
C:\Progra~1\PuTTY\plink.exe.

----------
messages: 6787
nosy: Zanchey
priority: bug
status: unread
title: ssh argument doesn't accept file names containing spaces on Windows

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1263>
____________________________________________________