[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: F11: Bug in sh-4.0 source build-in command

Dario Lesca wrote:
> Il giorno lun, 03/08/2009 alle 20.55 +0200, Michal Schmidt ha
> scritto:
>> Not a bug. You're running bash in POSIX mode (probably you ran
>> "sh").  In POSIX mode the current directory is not searched by the
>> source command. This is documented in the manpage.
> IMHO, this is a Bug.

No, it's not a bug.  The bash-3.2 behavior was the bug.

> "source: usage: source filename [arguments]"
> The command "source" take a "file" (-f, 644) and not a "executable" (-x,
> 755), like do "ls fil", "cat file", "sh file, "awk file", and many other
> command.
> So, if I run "source file", source must use "file", like do other
> command.

The bash builtins(1) manpage states this fairly clearly:

    source filename [arguments]

        Read and execute commands from filename in the current shell
        environment and return the exit status of the last command
        executed from filename. If filename does not contain a slash,
        file names in PATH are used to find the directory containing
        filename. The file searched for in PATH need not be
        executable. When bash is not in posix mode, the current
        directory is searched if no file is found in PATH. If the
        sourcepath option to the shopt builtin command is turned off,
        the PATH is not searched.

Also see bash author Chet Ramey's recent reply on the bash list:


Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
No sense being pessimistic, it probably wouldn't work anyway

Attachment: pgpXSjMuXAfDY.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]