This is the mail archive of the
mailing list for the Cygwin project.
Re: heeding suggestion
- To: ddeyoung at jps dot net, cygwin at sourceware dot cygnus dot com
- Subject: Re: heeding suggestion
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Wed, 20 Oct 1999 12:26:09 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- Daniel de Young <firstname.lastname@example.org> wrote:
> Please excuse the long delay in this response. My lovely ISP has been
> their e-mail system for a year now *sarc*
> curses.h is not part of the ANSI/POSIX compliance. You'll have to download
> ncurses package for this.
> RESP:I have ncurses (bin dist) installed and curses.h does exist in the path.
> vim uses it fine.
Hmm... Cygwin built or from some other package? You must have a cygwin built
> > Found: c:\cygnus\cygwin-b20\H-i586-cygwin32\bin\bash.exe
> > Found: D:\WINNT\cat.exe
> > Found: c:\cygnus\cygwin-b20\H-i586-cygwin32\bin\cat.exe
> > Warning: D:\WINNT\cat.exe hides
> > c:\cygnus\cygwin-b20\H-i586-cygwin32\bin\cat.exe
> Now this is real strange, in that you had the
> c:\cygnus\cygwin-b20\H-i586-cygwin32\bin listed first in the PATH.
> it should be the cygwin path hiding the D:\WINNT directory. Why do you have
> these programs in D:\WINNT\ anyway?
> RESP: This section doesn't seem to follow how I have them listed in .bashrc.
> Hmmm. I'll fix that. They are leftover from utils that I loaded and used
> before I found this cool package.
How are you starting bash? If you use the -login switch then .bashrc will not
get read. Issue bash --help for more on this.
BTW, I modify my PATH in my .bashrc file also. I advise it over taking the
default from cygwin, especially with your mount table. It makes since to do so
since you don't really want to muck with the Win32 version of PATH.
Earnie Boyd <mailto:email@example.com>
Newbies, please visit
(If you respond to the list, then please don't cc me)
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org