[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: Problem with default config.cache
From: |
Tim Van Holder |
Subject: |
Re: FW: Problem with default config.cache |
Date: |
Mon, 30 Jul 2001 21:55:09 +0200 |
> > . file
> > DESCRIPTION
> > The shell will execute commands from the file in the current
> environment.
> > If file does not contain a slash, the shell will use the search path
> > specified by to find the directory containing file. Unlike
> normal command
Note that the critical piece of information is missing (specified by
_what_). One assumes $PATH was intended, but it could just as easily
be meant to state "$PATH:.".
> > search, however, the file searched for by the dot utility need not be
> > executable. If no readable file is found, a non-interactive shell will
> > abort; an interactive shell will write a diagnostic message to standard
> > error, but this condition will not be considered a syntax error.
>
> The current directory fallback behaviour must be a bashism.
Actually, it's not a bashism either:
$ bash
bash-2.04$ help .
.: . filename
Read and execute commands from FILENAME and return. The pathnames
in $PATH are used to find the directory containing FILENAME.