From: John Wiersba <John.Wiersba@medstat.com>
To: "' Clark Sims '" <clarksimsgnu@my-Deja.com>,
"'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: Newbie questions
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <03F4742D8225D21191EF00805FE62B990205E29D@AA-MSG-01> (raw)
Message-ID: <19990831234900.12bh6OsVLCnYyw0senTrilWsrI8i9pTTBlcirwgsFQg@z> (raw)
> -----Original Message-----
> From: Clark Sims [ mailto:clarksimsgnu@my-Deja.com ]
<lots of SNIPs>
> How do I "see the bash man page"?
See below
> echo $PATH produces:
>
> /cygnus/CYGWIN~1/H-I586~1/bin:/cygnus/CYGWIN~1/H-I586~1/bin:d:
> /fsf/emacs-19.34/bin:d:/fsf/bin:/WINNT/system32:/WINNT:d:/CCLI
> B/libnt:d:/WATCOM/BINNT:d:/WATCOM/BINW:d:/util:.:d:/PROGRA~1/ULTRAEDT
>
> d:/fsf/emacs-19.34/bin contains emacs.exe
> but I can't run emacs unless I specify the full path
As another poster hinted, the colon is a path element separator, so
d:/anything won't work. Try
mount
mkdir /d
mount d: /d
and then put /d/anything in your path. There's more info about mount
scattered throughout the documentation/FAQ.
> d:/fsf/bin contains man.exe but I can't run man.
> Is the cygwin install supposed to contain man.exe?
I downloaded the man package from the franken ftp site, but if you already
have another man, then maybe that will work. I believe the man pages are
included in the install, but man.exe is not, for some reason.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~1999-08-31 23:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-25 7:53 John Wiersba [this message]
1999-08-31 23:49 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
2014-02-04 19:20 Newbie Questions mrushton
2014-02-04 20:52 ` Gary Johnson
2014-02-04 20:55 ` Marco Atzeri
2014-02-05 18:25 ` Mike Rushton
2014-02-05 18:30 ` Larry Hall (Cygwin)
2014-02-05 21:17 ` Warren Young
2014-02-05 21:30 ` Warren Young
2014-02-05 22:20 ` Andrey Repin
2014-02-05 22:35 ` Andrey Repin
2014-02-06 0:39 ` Warren Young
2014-02-06 1:05 ` Andrey Repin
2014-02-06 1:15 ` Warren Young
2014-02-06 8:20 ` Andrey Repin
2014-02-06 20:34 ` Warren Young
2014-02-05 21:44 ` Mike Rushton
2014-02-05 22:20 ` Andrey Repin
2014-02-05 22:05 ` Andrey Repin
2002-07-06 21:26 Newbie questions rick
2002-02-13 12:00 newbie questions marcin pakula
1999-08-25 5:02 Newbie questions Clark Sims
1999-08-25 5:08 ` Kim Poulsen
1999-08-31 23:49 ` Kim Poulsen
1999-08-25 8:06 ` Keith Starsmeare
1999-08-31 23:49 ` Keith Starsmeare
1999-08-31 23:49 ` Clark Sims
1999-08-24 8:08 John Wiersba
1999-08-31 23:49 ` John Wiersba
1999-08-24 6:26 Clark Sims
1999-08-24 6:35 ` Larry Hall (RFK Partners, Inc)
1999-08-31 23:49 ` Larry Hall (RFK Partners, Inc)
1999-08-24 13:06 ` Michael Hirmke
1999-08-31 23:49 ` Michael Hirmke
1999-08-31 23:49 ` Clark Sims
1999-01-31 23:52 Jan Hubicka
1998-04-02 9:35 Earnie Boyd
[not found] <199803221444.GAA20073@cygnus.com>
1998-04-02 9:35 ` Michael Hirmke
1998-02-28 23:38 Nagle, Adrian
1998-02-09 5:30 Earnie Boyd
1998-02-06 8:16 bash questions Eric Horowitz
1998-02-06 16:53 ` Newbie questions Silas S. Brown
1998-02-07 6:45 ` Benjamin Riefenstahl
1998-02-05 9:14 tar (four questions) (NBY) Earnie Boyd
1998-02-06 1:27 ` Newbie questions Francois Felix Ingrand
1998-02-06 11:19 ` Fergus Henderson
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=03F4742D8225D21191EF00805FE62B990205E29D@AA-MSG-01 \
--to=john.wiersba@medstat.com \
--cc=clarksimsgnu@my-Deja.com \
--cc=cygwin@sourceware.cygnus.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).