9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sl@9front.org
To: 9fans@9fans.net
Subject: Re: [9fans] inequality testing in shell
Date: Sun, 14 Jun 2015 18:54:33 -0400	[thread overview]
Message-ID: <11aa6d92b190b3db2d6e958e703e5723@ghost.inri> (raw)

     TEST(1)                                                   TEST(1)

     NAME
          test - set status according to condition

     SYNOPSIS
          test expr

     DESCRIPTION
          Test evaluates the expression expr. If the value is true the
          exit status is null; otherwise the exit status is non-null.
          If there are no arguments the exit status is non-null.

          The following primitives are used to construct expr.

          -r file    True if the file exists (is accessible) and is
                     readable.
          -w file    True if the file exists and is writable.
          -x file    True if the file exists and has execute permis-
                     sion.
          -e file    True if the file exists.
          -f file    True if the file exists and is a plain file.
          -d file    True if the file exists and is a directory.
          -s file    True if the file exists and has a size greater
                     than zero.
          -t fildes  True if the open file whose file descriptor num-
                     ber is fildes (1 by default) is the same file as
                     /dev/cons.
          -A file    True if the file exists and is append-only.
          -L file    True if the file exists and is exclusive-use.
          -Tfile     True if the file exists and is temporary.
          s1 = s2    True if the strings s1 and s2 are identical.
          s1 != s2   True if the strings s1 and s2 are not identical.
          s1         True if s1 is not the null string.  (Deprecated.)
          -n s1      True if the length of string s1 is non-zero.
          -z s1      True if the length of string s1 is zero.
          n1 -eq n2  True if the integers n1 and n2 are arithmetically
                     equal.  Any of the comparisons -ne, -gt, -ge,
                     -lt, or -le may be used in place of -eq.  The
                     (nonstandard) construct -l string, meaning the
                     length of string, may be used in place of an
                     integer.
          a -nt b    True if file a is newer than (modified after)
                     file b.
          a -ot b    True if file a is older than (modified before)
                     file b.
          f -older t True if file f is older than (modified before)
                     time t. If t is a integer followed by the letters
                     y(years), M(months), d(days), h(hours),
                     m(minutes), or s(seconds), it represents current
                     time minus the specified time.  If there is no
                     letter, it represents seconds since epoch.  You
                     can also concatenate mixed units.  For example,
                     3d12h means three days and twelve hours ago.

          These primaries may be combined with the following opera-
          tors:

          !         unary negation operator
          -o        binary or operator
          -a        binary and operator; higher precedence than -o
          ( expr )  parentheses for grouping.

          The primitives -b, -u, -g, and -s return false; they are
          recognized for compatibility with POSIX.

          Notice that all the operators and flags are separate argu-
          ments to test. Notice also that parentheses and equal signs
          are meaningful to rc and must be enclosed in quotes.

     EXAMPLES
          Test is a dubious way to check for specific character
          strings: it uses a process to do what an rc(1) match or
          switch statement can do.  The first example is not only
          inefficient but wrong, because test understands the pur-
          ported string "-c" as an option.

               if (test $1 '=' "-c") echo OK # wrong!

          A better way is

               if (~ $1 -c) echo OK

          Test whether `abc' is in the current directory.

               test -f abc -o -d abc

     SOURCE
          /sys/src/cmd/test.c

     SEE ALSO
          rc(1)

     BUGS
          Won't complain about extraneous arguments since there may be
          arguments left unprocessed by short-circuit evaluation of -a
          or -o.



             reply	other threads:[~2015-06-14 22:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 22:54 sl [this message]
2015-06-14 23:13 ` Neven Sajko
2015-06-14 23:30   ` Steve Simon
  -- strict thread matches above, loose matches on Subject: below --
2015-06-14 21:08 Neven Sajko
2015-06-14 21:28 ` Kurt H Maier
2015-06-14 22:11 ` Steve Simon
2015-06-15 13:14 ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=11aa6d92b190b3db2d6e958e703e5723@ghost.inri \
    --to=sl@9front.org \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).