From: "DEWI - N. Zacharias" <N.Zacharias@dewi.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: AW: [bulk] - Directory structuring
Date: Wed, 27 Jun 2012 07:06:00 -0000 [thread overview]
Message-ID: <8CCC8F85C5F2784387A32FAD835FB4E60A1D98CECC@server03.company.internal> (raw)
In-Reply-To: <34075389.post@talk.nabble.com>
Hi Paul,
>Von: PaulAThompson
>Gesendet: Mittwoch, 27. Juni 2012 00:09
>Betreff: [bulk] - Directory structuring
>
>
>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
[zac] As far as I can reproduce all windows/terminals under cygwin using the bash. So the reason for your problem might be located somewhere else.
>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
[zac] All of them should work! So what exactly is the reaction you get from the bash ??
Best regards
Norbert
DEWEK 2012, 11th German Wind Energy Conference, 7-8 November 2012 in Bremen
http://www.dewek.de/
--------------------------------------------------------------------------
Dipl. Phys.
Norbert Zacharias
Wind Measurements & Power Curve Measurements
DEWI GmbH
Ebertstrasse 96
26382 Wilhelmshaven
Germany
Tel.: +49 4421 4808 876
Fax: +49 4421 4808 843
Email: N.Zacharias@dewi.de
Home: http://www.dewi.de
DEWI GmbH - Deutsches Windenergie-Institut, Wilhelmshaven
Commercial Register No.: Amtsgericht Oldenburg, HRB 130241
Managing Director: Jens Peter Molly
P Please consider the environment before printing this 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
next prev parent reply other threads:[~2012-06-27 7:06 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 ` DEWI - N. Zacharias [this message]
2012-06-27 22:04 ` AW: [bulk] - " PaulAThompson
2012-06-27 22:17 ` PaulAThompson
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=8CCC8F85C5F2784387A32FAD835FB4E60A1D98CECC@server03.company.internal \
--to=n.zacharias@dewi.de \
--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).