Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3E6F99BE.5050507@pobox.com> Date: Wed, 12 Mar 2003 15:34:06 -0500 From: Tom Roche Reply-To: Tom_Roche AT pobox DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwinized XSL processor? (or sed for path transform?) References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit On Tue, 11 Mar 2003, Tom Roche wrote: >> my script does a lot of path translations like >> cygpath="/g/eclipse/builds/foo" >> winpath="g:\\eclipse\\builds\\foo" >> and it doesn't iterate over the paths. (Not a big deal, but it >> offends my software aesthetics :-) Igor Pechtchanski Tue, 11 Mar 2003 17:57:49 -0500 (EST) > I suspect the "-p" and "-f" options to cygpath might be of some help > to you. No, but "cygpath -a" is a great help! I can iterate over the windows paths, and get the cygwin paths from them with `cygpath -a $winpath`. Thanks for the suggestion! -- 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/