From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-
ow...@cygwin.com] On Behalf Of John Emmas
Sent: Monday, September 28, 2009 4:43 AM
From: Mike Ayers
If you set PATH absolutely in .bash_profile, the right thing will
happen.
You may want to copy the initial value of PATH into
- Original Message -
From: Mike Ayers
If you set PATH absolutely in .bash_profile, the right thing will happen.
You may want to copy the initial value of PATH into another exported env
var, so that you can see if there have been changes to the default path.
Hi Mike. If I can find
- Original Message -
From: Ken Brown
Most of the extra entries probably come from the various bash startup
files (including /etc/profile). These startup files will be invoked every
time you start a new bash login shell.
It looks like you're right about this Ken. Many of the scripts
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-
ow...@cygwin.com] On Behalf Of John Emmas
Sent: Friday, September 25, 2009 2:51 AM
It looks like you're right about this Ken. Many of the scripts and
batch
files just blindly add their directory requirements to my path without
- Original Message -
From: Mike Ayers
Subject: RE: Path problem with xterm
Are you perhaps modifying PATH in .bashrc?
No Mike, not as far as I can tell. In fact it's the original .bashrc that
was installed with Cygwin. I haven't edited it and I can't see anything in
it that refers
On 9/24/2009 12:04 PM, John Emmas wrote:
If I open a bash terminal in cygwin, then I create an xterm (either by
running startxwin.bat or by running the relevant lines from it manually)
then I type set, my environment settings get listed. Among them is my
current PATH variable. However, the
