This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

RE: Path problem with xterm

From: "Mike Ayers" <mike_ayers at tvworks dot com>
To: <cygwin-xfree at cygwin dot com>
Date: Fri, 25 Sep 2009 10:14:10 -0700
Subject: RE: Path problem with xterm
References: <003201ca3d30$a5ce3680$4001a8c0@mycomputer> <4ABBD0E9.4050100@cornell.edu> <006f01ca3dc5$b0469db0$4001a8c0@mycomputer>
Reply-to: cygwin-xfree at cygwin dot com

> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree-
> owner@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
> checking whether the path already contained them.

	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.


	HTH,

Mike

Follow-Ups:
- Re: Path problem with xterm
  - From: John Emmas

References:
- Path problem with xterm
  - From: John Emmas
- Re: Path problem with xterm
  - From: Ken Brown
- Re: Path problem with xterm
  - From: John Emmas

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]