Lines Matching refs:where

1185 and it must work even in a pathological situation where
1285 In the opposite situation, where you want the last operand to be
1411 @c Append the following warning to -L where appropriate (e.g. chown).
2581 is @samp{Page @var{number}} where @var{number} is the decimal page
3388 Split @var{input} to @var{chunks} output files where @var{chunks} may be:
3415 When the input is a pipe or some other special file where the size
3674 Suppress the generation of zero-length output files.  (In cases where
4060 Binary mode is the default on systems where it's significant,
4140 Use network byte order (big endian) where applicable:
4515 merge; merging is provided because it is faster, in the case where it
4617 @samp{0x} or @samp{0X}, where those numbers are not fixed width,
4776 where @var{f} is the number of the field to use, and @var{c} is the number
5177 @command{shuf} has three modes of operation that affect where it
6264 Anyhow, that's where tsort came from.  To solve an old problem with
6619 character @samp{0} or has the form @var{m.n} where the file number, @var{m},
7084 caution in multibyte locales where its meaning is not always clear
7130 where each possible input byte represents a single character.
7137 where characters are represented by byte sequences instead of by
7138 individual bytes, or where data might contain invalid bytes that are
7571 @option{-@var{tab1}[,@var{tab2}]@dots{}}, where tab stops must be
7838 where @var{word} is the quoting style (@pxref{Formatting the file names}).
7967 @samp{total @var{blocks}}, where @var{blocks} is the file system allocation
8213 directories, where sorting can take some time.
8443 @command{ls} uses tabs where possible in the output, for efficiency.  If
8517 List timestamps using @var{format}, where @var{format} is interpreted
9115 arguments where it then sees two files with the same inode number.
9925 Sending an @samp{INFO} signal (or @samp{USR1} signal where that is unavailable)
10875 a directory; on those where it is allowed, only the super-user can do
10915 location where the relative symlink will be created, so that
10986 where this is not supported by the kernel, this option creates a
12454 Failure includes the case where no output is generated, so you can
12723 List timestamps using @var{format}, where @var{format} is interpreted
12857 Report information about the file systems where the given files are located
13347 digits, as opposed to C where it can have an unlimited number of
13357 @samp{\0@var{ooo}} where @var{ooo} is 0 to 3 octal digits.  If
13518 where an unsuccessful command is needed.
13549 where a successful command is needed, although the shell built-in
14066 Returns the first position in @var{string} where the first character in
14486 result is @samp{//} on platforms where @var{//} is distinct from
14487 @var{/}, and @samp{/} on platforms where there is no difference.
14557 result is @samp{//} on platforms where @var{//} is distinct from
14558 @var{/}, and @samp{/} on platforms where there is no difference.
14688 race condition where the attacker can create an appropriately named
14790 time between generating the name and using it where another process
15642 They are set with the syntax @samp{name value}, where the names are
15773 in cases where the system may be in a state where serial transmission
15821 4000000 where the system supports these.
15945 then print @samp{context=@var{c}}, where @var{c} is the security context.
16479 is easy to sort in the usual case where years are in the range
16666 @samp{MMDDhhmm[[CC]YY][.ss]} where each two-letter
17593 with systems where this is allowed for non-privileged users.}.
19388 the default format is @samp{%.@var{p}f}, where @var{p} is the minimum
19465 internally.  For example, on the x86 platform, where the internal
19594 where you need a simple, general purpose tool, it's just the thing.
19599 exactly when and where to use each tool; you won't catch him hammering nails
19638 and ``standard error''.  Briefly, ``standard input'' is a data source, where
19641 card reader.  Similarly, ``standard output'' is a data sink, where data goes
19642 to.  The program should neither know nor care where this might be.
19662 user will probably never see it.  So programs need a place where they can send
19768 This is where @command{uniq} comes in.  The @command{uniq} program reads its
20023 dictionary.  Here is where the @command{comm} command comes in.
20074 Combining programs with appropriate plumbing leads to results where