[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDE2MTldIE5ldyAtIHN2biBjbGllbnQgYW5kIGN5Z3dpbg==?=
From:       timot () tigris ! org
Date:       2003-11-28 8:39:40
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=1619
                  Issue #:|1619
                  Summary:|svn client and cygwin compatibility
                Component:|subversion
                  Version:|current
                 Platform:|PC
                      URL:|
               OS/Version:|Windows XP
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|FEATURE
                 Priority:|P3
             Subcomponent:|cmdline client
              Assigned to:|issues@subversion
              Reported by:|timot






------- Additional comments from timot@tigris.org Fri Nov 28 00:39:40 -0800 2003 -------
Coming from the unix world, I tend to use the cygwin shell and write scripts for
cygwin when I'm using windows. While the svn command line client works fine when
executed from the cygwin shell, there is one small trouble with it. It outputs
file names using backslashes as seperators. While it is the OS-correct default,
I think an option to output file paths with forward slashes would be great. Atm
when I want to process the output of svn status, I have to pipe through sed to
rework the file paths:

$ svn status | grep ^? | cut -b 2- | sed -e 's/\\/\//g'
      docs/developer/CHANGES.orig
(instead of docs\developer\CHANGES.orig etc.)

A switch in the svn global options would make my life easier ..

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

[prev in list] [next in list] [prev in thread] [next in thread]