Check an environment variable and/or command line options.
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.
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 23 17:57:54 2003