Re: bash-question

[Stephan Kulka <e9626471@student.tuwien.ac.at>]

> On Mon, Dec 25, 2000 at 10:21:52AM +0100, Stephan Kulka wrote:
> > That's quite a newbie question, but I don't know what to do.
> > Yesterday I made a new directory for programming, I added this directory
> > with export to my PATH. Yesterday everything went fine, but today I always
> > get the error command not found. I checked my PATH, it i so.k. and the
> > compiled programs work when I type ./foo
> > What's wrong??
> 
> Today you logged on afresh, and so the path has to be set again.

The strange thing is that I just checked with echo $PATH and I still found
my path I exported yesterday. But when I loooked closer I found out that,
I used a semicolon to separate my directories instead of a colon. Is
there away to change that.



> To free you from the burden to ajust your path (and other prefs.)
> each time you logon, most shells alow you to set those prefs. in a
> *rc (run-command) file. Bash (probably the shell you are using)
> has ~/.bash_profile and ~/.bashrc.  The first gets run for each
> 'login' shell, the latter only for non-login shells. (man bash
> for more info; ~/ gets translated to the full path to your home
> directory) 

[snip]

Thanks for the good advice, I will edit my startup files as proposed.

Stephan