$PWD

[dmartin at LanCity.COM (Derek Martin)]

On Wed, 28 Jul 1999, Subba Rao wrote:

> Thank you for replying. Is this a BASH shell feature?

They are all features of bash, but the colon in the path is not
bash-specific... I believe it exists in all bourne shell derivitives.


> >
> >> Yet, I can excute the programs in the current directory. When I run "echo $PATH", the "."
> >> does not appear in the list.
> >
> >There are several possibilities.  When bash starts, it sources
> >$HOME/.bash_profile if it is a login shell, or $HOME/.profile if
> >.bash_profile doesn't exist.  Also all interactive bash shells (login or
> >not) source /etc/bashrc and $HOME/.bashrc whenever a new copy of bash
> >starts.
> >
> >Check these files.  Also, many people do not realize that if the path
> >statement ends in a colon, it has the same effect as including . in your
> >path, i.e.
> >
> >PATH=/bin:
> >
> >is the same as 
> >
> >PATH=/bin:.

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).