From: PaulAThompson <patjahsd@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Directory structuring
Date: Wed, 27 Jun 2012 22:17:00 -0000 [thread overview]
Message-ID: <34083438.post@talk.nabble.com> (raw)
In-Reply-To: <34075389.post@talk.nabble.com>
I have solved this problem. Please do not reply any more.
Solution:
1) Ensure that cygwin was using a cygwin-native perl
2) Routine use of d2u to get the files to have *nix endings for lines not
windows endings
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
>
> c:/subdir
>
> I have tried a number of manner of using cd within the bash shell to
> change directories without any success
>
> Is there a simple guide to the path specifications? This seems simple, but
> I cannot figure out the correct specification
>
> Within the bash shell, I have tried
>
> cd /cygdrive/c/subdir
> cd "/cygdrive/c/subdir"
> cd c:/subdir
> cd "c:/subdir"
>
> None of these work
>
>
--
View this message in context: http://old.nabble.com/Directory-structuring-tp34075389p34083438.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
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
prev parent reply other threads:[~2012-06-27 22:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 22:09 PaulAThompson
2012-06-26 22:19 ` Larry Hall (Cygwin)
2012-06-26 22:35 ` PaulAThompson
2012-06-26 22:45 ` PaulAThompson
2012-06-26 23:00 ` Larry Hall (Cygwin)
2012-06-27 7:06 ` AW: [bulk] - " DEWI - N. Zacharias
2012-06-27 22:04 ` PaulAThompson
2012-06-27 22:17 ` PaulAThompson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34083438.post@talk.nabble.com \
--to=patjahsd@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).