Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Authentication-Warning:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Tue, 11 Mar 2003 17:57:49 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	Tom Roche <Tom_Roche AT pobox DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: cygwinized XSL processor? (or sed for path transform?)
In-Reply-To:	<3E6E60B4.1010102@pobox.com>
Message-ID:	<Pine.GSO.4.44.0303111756300.11568-100000@slinky.cs.nyu.edu>
Importance:	Normal
MIME-Version:	1.0

On Tue, 11 Mar 2003, Tom Roche wrote:

> [snip]
> As a result, my script does a lot of path translations like
>
> cygpath="/g/eclipse/builds/20030311_1000-WB210-AD-V51D-W2/eclipse/plugins"
> winpath="g:\\eclipse\\builds\\20030311_1000-WB210-AD-V51D-W2\\eclipse\\plugins"
>
> and it doesn't iterate over the paths. (Not a big deal, but it offends
> my software aesthetics :-)
> [snip]
> Alternatively, if I had more sed chops, I could script the path
> transformation, but I don't know how to do that either. (Could someone
> tell me how to do that?)

I suspect the "-p" and "-f" options to cygpath might be of some help to
you.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -