On 2002-04-17 20:32:04 Branko Čibej wrote:
>Daniel Stenberg wrote:
>>I vote for requiring spaces to be escaped (possibly with backslashes like
>>"\ "), otherwise use them as separators. It would make existing
>>space-for-separator using EDITOR strings to work as before, and new ones
>>using-space-in-command-name could just learn to follow the escaping.
>>
>Hm, so you're gonna parse escapes in $EDITOR in the svn code? What say
>we just forget it and call system() for this particular case, and let
>the shell handle that for us? For Windows, we just have to document that
>if you have spaces in the path, you must enclose the program name in
>double quotes, and cmd.exe (or command.com) will just magically DTRT.
This has the great advantage of being completely consistent with the
way Windows already does this sort of thing. It is actually far more common
in Windows than Unix, because every file extension can have a program
associated with it which is used to open it when double-clicked.
Peter.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 18 10:35:00 2002