Message-id: <4FEA3545.5030507@cygwin.com>
Date: Tue, 26 Jun 2012 18:18:45 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: Directory structuring
References: <34075389.post@talk.nabble.com>
In-reply-to: <34075389.post@talk.nabble.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 6/26/2012 6:09 PM, PaulAThompson wrote:
>
> I am very confused about the correct manner of defining directory paths under
> cygwin, perl, and bash. I cannot determine the correct manner. Using the
> cygwin window, I navigate to locations using
>
> cd /cygdrive/c/subdir
>
> Using a bash shell to run a perl process under the shell and passing in a
> directory, I must use a windows-style specification with *nix forward
> slashes

If you're using Cygwin's Perl, then you don't need to worry about
windows-style paths.  If you must, for some reason, use the Windows-native
Perl, then check out 'man cygpath'.  It will handle the file path
conversions for you so you can stick with POSIX paths when you type.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple