You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by solo turn <so...@yahoo.com> on 2003/05/23 01:34:05 UTC

cygwin and \ or /

for command line usage out of cygwin it is not very practical that
svn uses \ as directory separator and expects / on the command line.
you cannot copy the path any more.

can i somehow configure svn to use / in the output of "svn st", or
"svn up" so i could use copy-paste again?

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: cygwin and \ or /

Posted by solo turn <so...@yahoo.com>.
its not only cygwin, but also in windows cmd the following works:
C:\>cd "doc*/adm*"
C:\Documents and Settings\Administrator>

so imo, no option would be necessary i suppose.



--- Branko Čibej <br...@xbc.nu> wrote:
> 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   <br...@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
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: cygwin and \ or /

Posted by solo turn <so...@yahoo.com>.
we could rename the option to:
- display path in operating system style
- display path in url style (without the server)
- display path in url style (with server)

then it would not break notation :)

the copying was a very useful feature in daily work and the
convenient thing was that you can paste it to local path (svn takes
it), and to the url (and its a valid url).

now it has become a fiddeling, cd'ing, quoting, and rewriting task.

*duck*

--- Branko Čibej <br...@xbc.nu> wrote:
> 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   <br...@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
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: cygwin and \ or /

Posted by Branko Čibej <br...@xbc.nu>.
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   <br...@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

Re: cygwin and \ or /

Posted by Jonathan Smith <jo...@members.limitless.org>.
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


Re: cygwin and \ or /

Posted by Branko Čibej <br...@xbc.nu>.
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   <br...@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

Re: cygwin and \ or /

Posted by Jonathan Smith <jo...@members.limitless.org>.
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?

Simply insert a filter around any argument that is a file name to convert 
from either slash to the system's slash.  For unix, this would render the 
'\' as an invalid character.  But, the clarity would be preferable.  

I've seen this done before, but I don't know where.

Certainly, I'd like to see this behavior on Windows.  Unix would be a 
battle of consistency (on both sides).

j.


On Fri, 23 May 2003, [UTF-8] Branko Čibej wrote:

> solo turn wrote:
> 
> >did this change recently? i had the impression i always copied the
> >paths .... hmmm. maybe its the beer.
> >
> Yes, it did change recently, and it'll change some more -- we're not
> quite consistent in the client yet. The goal is to have the client on
> Windows display all paths with \ separators, so that you can cut&paste
> in the Windows command line.
> 
> Cygwin can never be a primary target, because it's not the default shell
> on Windows (BTW, I also use cygwin almost exclusively). But Cygwin does
> understand \-separated paths, as long as you take care to avoid shell
> escaping.
> 
> >
> >--- Branko ÄŒibej <br...@xbc.nu> wrote:
> >  
> >
> >>solo turn wrote:
> >>
> >>    
> >>
> >>>for command line usage out of cygwin it is not very practical that
> >>>svn uses \ as directory separator and expects / on the command
> >>>      
> >>>
> >>line.
> >>    
> >>
> >>>you cannot copy the path any more.
> >>>
> >>>can i somehow configure svn to use / in the output of "svn st", or
> >>>"svn up" so i could use copy-paste again?
> >>>
> >>>      
> >>>
> >>Yes. You can edit svn_private_config.hw -- define
> >>SVN_LOCAL_PATH_SEPARATOR to '/' and recompile.
> >>
> >>Or, of course, if you're using cygwin, you can enclose the paths in
> >>single quites -- e.g., 'C:\foo' instead of C:\foo. That'll just
> >>work.
> >>
> >>
> >>
> >>-- 
> >>Brane ÄŒibej   <br...@xbc.nu>   http://www.xbc.nu/brane/
> >>
> >>    
> >>
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >The New Yahoo! Search - Faster. Easier. Bingo.
> >http://search.yahoo.com
> >
> >  
> >
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org


Re: cygwin and \ or /

Posted by Branko Čibej <br...@xbc.nu>.
solo turn wrote:

>did this change recently? i had the impression i always copied the
>paths .... hmmm. maybe its the beer.
>
Yes, it did change recently, and it'll change some more -- we're not
quite consistent in the client yet. The goal is to have the client on
Windows display all paths with \ separators, so that you can cut&paste
in the Windows command line.

Cygwin can never be a primary target, because it's not the default shell
on Windows (BTW, I also use cygwin almost exclusively). But Cygwin does
understand \-separated paths, as long as you take care to avoid shell
escaping.

>
>--- Branko ÄŒibej <br...@xbc.nu> wrote:
>  
>
>>solo turn wrote:
>>
>>    
>>
>>>for command line usage out of cygwin it is not very practical that
>>>svn uses \ as directory separator and expects / on the command
>>>      
>>>
>>line.
>>    
>>
>>>you cannot copy the path any more.
>>>
>>>can i somehow configure svn to use / in the output of "svn st", or
>>>"svn up" so i could use copy-paste again?
>>>
>>>      
>>>
>>Yes. You can edit svn_private_config.hw -- define
>>SVN_LOCAL_PATH_SEPARATOR to '/' and recompile.
>>
>>Or, of course, if you're using cygwin, you can enclose the paths in
>>single quites -- e.g., 'C:\foo' instead of C:\foo. That'll just
>>work.
>>
>>
>>
>>-- 
>>Brane ÄŒibej   <br...@xbc.nu>   http://www.xbc.nu/brane/
>>
>>    
>>
>
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Search - Faster. Easier. Bingo.
>http://search.yahoo.com
>
>  
>


-- 
Brane Čibej   <br...@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

Re: cygwin and \ or /

Posted by solo turn <so...@yahoo.com>.
did this change recently? i had the impression i always copied the
paths .... hmmm. maybe its the beer.

--- Branko Čibej <br...@xbc.nu> wrote:
> solo turn wrote:
> 
> >for command line usage out of cygwin it is not very practical that
> >svn uses \ as directory separator and expects / on the command
> line.
> >you cannot copy the path any more.
> >
> >can i somehow configure svn to use / in the output of "svn st", or
> >"svn up" so i could use copy-paste again?
> >
> Yes. You can edit svn_private_config.hw -- define
> SVN_LOCAL_PATH_SEPARATOR to '/' and recompile.
> 
> Or, of course, if you're using cygwin, you can enclose the paths in
> single quites -- e.g., 'C:\foo' instead of C:\foo. That'll just
> work.
> 
> 
> 
> -- 
> Brane Čibej   <br...@xbc.nu>   http://www.xbc.nu/brane/
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: cygwin and \ or /

Posted by Branko Čibej <br...@xbc.nu>.
solo turn wrote:

>for command line usage out of cygwin it is not very practical that
>svn uses \ as directory separator and expects / on the command line.
>you cannot copy the path any more.
>
>can i somehow configure svn to use / in the output of "svn st", or
>"svn up" so i could use copy-paste again?
>
Yes. You can edit svn_private_config.hw -- define
SVN_LOCAL_PATH_SEPARATOR to '/' and recompile.

Or, of course, if you're using cygwin, you can enclose the paths in
single quites -- e.g., 'C:\foo' instead of C:\foo. That'll just work.



-- 
Brane Čibej   <br...@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