Jonathan Smith wrote:
>Check an environment variable and/or command line options.
>
Excuse me? Have an *option* to decide whether we should display paths in
the OS's native style or not? Is it just me, or is the world really
going insane?
On Windows, Subversion will use \ as the path separator for output. It
will accept both \ and / on input. There will be no vote. I have spoken.
"Hear this and tremblingly obey!"
>j.
>
>
>On Fri, 23 May 2003, [UTF-8] Branko ÄŒibej wrote:
>
>
>
>>Jonathan Smith wrote:
>>
>>
>>
>>>Since windows has no concept of an escape character to my knowledge (in
>>>Microsoft's idiot-user based paradigm, "Who could possibly understand such
>>>a horribly complex thing?), and since '/' is an illegal character on
>>>windows, why not accept both slashes all the time?
>>>
>>>
>>>
>>We do, and we will. It's not about accepting both slashes, it's about
>>_displaying_ then. We're now displaying a mix of / and \, and moving
>>towards using \ exclusively. Then solo wants to cut&paste that output in
>>the cygwin bash shell. Cygwin programs will, of course, accept \ as a
>>separator, but the paths have to be quoted to avoid shell escaping.
>>
>>Lots of Windows command-line programs won't accept /, tbough.
>>
>>
>>
>>
>>
>>
>
>
>
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 23 18:06:57 2003