> What if we were to introduce a putty-specific URL:
> 
> putty://droundy@darcs.net:foo/bar?
> 
> Then we wouldn't need to guess at runtime how to call ssh.

I'd suggest putty://droundy@darcs.net/foo/bar (with a slash instead of a 
colon separating host from path) in order to make it legal URL syntax.

At the risk of getting off-topic for this bug report, I'd like to 
suggest that the SSH syntax be amended to support URL style as well.  My 
reason is pragmatic: there's currently no way to describe an ssh 
repository on a non-standard port.  You have to remember to set SSH_PORT 
before running any darcs commands on that repo (and un-set it when 
you're done).  URL syntax would allow something like 
ssh://droundy@darcs.net:10022/foo/bar to be used on command lines and 
stored in prefs/repos.  The port is, afterall, a property of the remote 
repository, not of the local machine or local login session.
-- 
Dennis Lambe Jr.
Preferred Utilities
<dlambe@preferred-mfg.com>

"The key to performance is elegance, not battalions of special cases."
--Jon Bentley and Doug McIlroy

Splitting this off from issue504, msg1979

The reason for this would be to provide a way to describe an SSH repository on a
non-standard port.  

I'm adding Matthew to this because I figure the Patch-Tag folks would be
interested.  Dennis last volunteered to work on this in 2007 but after two
years, I think it's up for grabs :-)

Note: if it did something like this we might be able to think about simplifying
the filepath handling code since we wouldn't have to guess if we have a remote
path or not.  But a such a simplification should be treated with care because we
don't want to do it in a way that confuses some core (repo-level and down) of
Darcs.  Anyway, that's for a different ticket.

> I'd suggest putty://droundy@darcs.net/foo/bar (with a slash instead of a 
> colon separating host from path) in order to make it legal URL syntax.

Please take care to be compatible with the de facto standard for ssh
URLs, where a single slash means a path relative from home, while
a double slash an absolute path:

  ssh://jch@ssh.darcs.net/public_html/repos/darcs/

but

  ssh://jch@ssh.darcs.net//usr/local/repos/darcs/

> At the risk of getting off-topic for this bug report, I'd like to 
> suggest that the SSH syntax be amended to support URL style as well.

Seconded.  Mostly because I keep getting confused (you need to use
ssh-style syntax with darcs and rsync, and URL syntax with unison).

                                        Juliusz

On 8/26/2010 11:04, Dennis Lambe wrote:
>
> Dennis Lambe<dlambe@preferred-mfg.com>  added the comment:
>
>> What if we were to introduce a putty-specific URL:
>>
>> putty://droundy@darcs.net:foo/bar?
>>
>> Then we wouldn't need to guess at runtime how to call ssh.
>
> I'd suggest putty://droundy@darcs.net/foo/bar (with a slash instead of a
> colon separating host from path) in order to make it legal URL syntax.

A more accurate URL would be: putty://droundy@darcs.net/~/foo/bar (SSH 
path's are relative to home directory).

--
--Max Battcher--
http://worldmaker.net

Florent said this was in progress (in issue1970).

The following patch sent by Florent Becker <florent.becker@ens-lyon.org> 
updated issue issue1970 with
status=resolved;resolvedin=2.8.0 HEAD

* resolve issue1970: allow ssh:// urls 
Ignore-this: 90ada77620504d0e4f1183a401e47da1