Re: Does [ -f FILE ] have a bug on testing a symlink ?

[Hans J Albertsson]

The current behaviour is according to the intended functionality of symlinks when they first appeared, i e to create first-rank local references across få boundaries. cf hard links.

Hans J. Albertsson
>From my Nexus 5

Den 10 feb 2015 10:04 skrev "Jonathan Hankins" <jhankins@homewood.k12.al.us>:

$ touch foo

$ ln -s foo bar

$ [[ -f foo ]] && [[ ! -h foo ]] && echo "exists and is not a symlink"

exists and is not a symlink

$ [[ -f bar ]] && [[ ! -h bar ]] && echo "exists and is not a symlink" 

$

-Jonathan Hankins

On Mon, Feb 9, 2015 at 6:00 PM, Cheng Rk <crquan@ymail.com> wrote:

On Monday, February 9, 2015 3:13 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
Cheng Rk <crquan@ymail.com> writes:

>> Then the builtin test help need a documentation fix, right?

You're addressing different lines but I am saying this line is inaccurate, right?


-f FILE        True if file exists and is a regular file.


Is there really a simple regular file test existing?

> test: test [expr]
    Evaluate conditional _expression_.

    Exits with a status of 0 (true) or 1 (false) depending on
    the evaluation of EXPR.  Expressions may be unary or binary.  Unary
    expressions are often used to examine the status of a file.  There
    are string operators and numeric comparison operators as well.

    The behavior of test depends on the number of arguments.  Read the
    bash manual page for the complete specification.

--

------------------------------------------------------------------------

Jonathan Hankins    Homewood City Schools

The simplest thought, like the concept of the number one,

has an elaborate logical underpinning. - Carl Sagan

jhankins@homewood.k12.al.us

------------------------------------------------------------------------