This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: [patch] adding ~/bin to path
- To: <cygwin at sources dot redhat dot com>
- Subject: RE: [patch] adding ~/bin to path
- From: "Erdely, Michael" <mike at erdelynet dot com>
- Date: Sun, 3 Dec 2000 00:26:19 -0500
So... I guess I don't understand the problem. If you want system wide shell
changes, you add them to /etc/profile. If you want user specific changes,
you add them to (in this case) $HOME/.bashrc.
I'd make the global changes in /etc/profile and be done with it. If you add
$HOME/bin or ~/bin to the path, you'll reach your goal.
Or maybe I'm oversimplifying.
-ME
-----Original Message-----
From: cygwin-owner@sources.redhat.com
[mailto:cygwin-owner@sources.redhat.com]On Behalf Of Chris Abbey
Sent: Sunday, December 03, 2000 12:22 AM
To: cygwin@sources.redhat.com
Subject: RE: [patch] adding ~/bin to path
At 23:56 12/2/00 -0500, Erdely, Michael wrote:
>Pardon me if I misunderstand, but I just added this line to ~/.bashrc:
>export PATH=$HOME/bin:$PATH
>
>Exited bash and reopened bash.
>echo $PATH returned the old path with "/home/mike/bin:" in front of it.
yup, that's the objective. But ~/.bashrc isn't shipped by default,
/etc/profile is. Putting it in ~/.bashrc also puts the responsibility
on each user, whereas putting it in /etc/profile has the system
do it, just like every *nix I've ever worked on.
now the forces of openness
have a powerful and
unexpected new ally
http://ibm.com/linux/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com