Re: .bash_profile question.

[Cameron Simpson <cs zip com au>]

On 15:20 19 May 2002, Dan Gordon <invg4 cogeco ca> wrote:
| I have added PATH=$PATH:/usr/local/kde/bin
| to my .bash_profile

Personally, I like to add
	export PATH
after that. FOr $PATH it doesn't matter so much (it's already exported), but
for arbitrary other variables they may well be "new", and so need this. So I
do it for them all.

| But im still not getting the effect i want, is there somthing im missing or 
| have not done?  What im trying to do is install mosfets liquid and the last 
| step is to add /usr/local/kde/bin to my path.

It's possible you have the (misconfigured as installed) GUI X setup.
Are you running a GUI login or a console login?

Typically the GUIs run new terminals as non-login terminals (which is
sane).  But they haven't sourced your .profile (or .bash_profile). This
is the root cause of all the evil advice you see on the lists about
putting $PATH changes and other environment settings in your .bashrc -
that way they do have immediate effect, but at the price of running all
that crap for _every_ new shell. Stupid and clumsy.

If this is a systemwide install (and an app egenrally is, even if you're
the only user), make a file like this:

	#!/bin/sh
	# mosfets PATH config
	PATH=$PATH:/usr/local/kde/bin
	export PATH

in the file

	/etc/profile.d/mosfets.sh

This will be sourced for all users. Now logout and log in and see if
it worked.

Cheers,
--
Cameron Simpson, DoD#743        cs zip com au    http://www.zip.com.au/~cs/

Just because Unix is a multiuser system doesn't mean I want to share it with
anybody!	- Paul Tomblin, in rec.aviation.military