clear tha the default date use space-padded day of month.
Replace "directive" with "conversion specifier" to be consistent
with POSIX. All uses changed.
Fix menu RHS to match actual directive lists.
(Time conversion specifiers): Renamed from Time directives.
Use @samp consistently, sometimes instead of @code.
Consistently ention which specifiers are GNU extensions.
Give more examples (in some cases, instead of ranges).
Say why %F is preferred for dates.
(Date conversion specifiers): Renamed from Date directives.
Likewise for other changes.
(Padding and other flags): Correct the description.
Document #. Give an example for %9B.
GNU extensions.
For %p and %P, mention handling of noon and midnight.
For %s, use ISO 8601, and mention handling of leap seconds.
For %S, clarify mention of leap seconds.
For %T, say that it's the same as %H:%M:%S.
For %X, don't say that it must be the same as %H:%M:%S.
For %z and %Z, clarify which time zones are used. These options
are now affected by --date, so don't claim that they're not.
(Date directives): %C is now all but the last two chars of %Y.
For %D, say that it's equivalent to %m/%d/%y.
For %e, use blank in example.
For %h, use @code for %b.
For %Y, mention what happens with outlandish years.
(Padding and other flags): Renamed from Padding.
Mention that the flags are GNU extensions.
Mention the 0 and ^ flags.
Mention field widths an modifiers.
(Examples of date): - is a flag, not a modifier.
capitalization, and sort order to match --help output. Mention %c
for file systems. Say that %s is the "Fundamental block size",
since that is what POSIX says.
"subdirectory not found", since top-level trouble is now serious.
(dircolors invocation): Quote argument to eval. Problem reported
by Stephane Chazelas.
than :|. Problem reported by Dan Jacobson.
Use "seek=2GiB" rather than the wordier "seek=`echo '2^31'|bc`".
Say "KiB" not the (inaccurate) "kilobytes".
Similarly for "GiB" and "gigabytes".
an operand.
(Formatting the file names): Warn that even with -N unprintable
chars are still printed as '?' some times.
(rm invocation): Reword rm -d to note that it's sometimes useful
on non-directories.
(logname invocation, users invocation, who invocation):
The utmp and wtmp file names vary from system to system.
example of obsolete usage, since the POSIX consensus is that "head -1"
could be supported even if we don't yet have clear consensus on "head
-10". See today's revision to the SUS FAQ
<http://www.opengroup.org/austin/papers/single_unix_faq.html>.
OS limits, not file system limits. Component length checks
apply to all components, not merely to existing ones. Say
that nonexistent names are not errors. For -p, omit all
checks based on the underlying file system, not merely length
checks. Explain what the portabile file name character set is.
(printf invocation): builtin -> built-in, for consistency
with POSIX terminology.
(test invocation, pwd invocation):
Use specific rather than generic language to warn about
built-in commands.
(chroot invocation, env invocation, nice invocation, nohup invocation):
Warn that command must not be a special built-in.
(env invocation): Warn about environment variables with unusual
spellings, or duplicates.
options.
(tr invocation, echo invocation, printf invocation, test invocation,
expr invocation, basename invocation, chroot invocation,
nice invocation, nohup invocation, seq invocation):
This program doesn't reorder options.
(tr invocation): Mention --help, --version, --.
(echo invocation): Mention that -- isn't special.
(test invocation): Mention that the expression is optional,
and that test ! EXPR is like ! test EXPR.
(expr invocation): Mention --help, --version.
and FreeBSD compatibility. Add support for XSI syntax
(POSIX 1003.1-2004). Rename -s[N] to -S N. Remove documentation
for -h. -i is now -t dI (not d2) and -l is now -t dL (not d4).
rather than "tabstop".
(unexpand invocation): Use "blank" rather than "space" when
POSIX requires "blank". Define "blank". Initial blanks are
converted even if there's just one. For -a, convert two or
more blanks only if they occur just before a tab stop.
group must always be preceded by separator.
"chown : file" and "chown '' file" don't change the owner or group.
Update the explanation of what happens to the set-user-ID or
set-group-ID bits, e.g., they sometimes are not cleared if they
denote mandatory locking. Change "find"-oriented examples to use
chown -h.
stdin/stdout only when it is an operand, not when it is an
option-argument.
(shred invocation): "shred -- -" is equivalent to "shred -",
not to "shred ./-".
(tee invocation): "tee -" means to copy (again) to stdout.
how it affects the scheduling priority. (The old documentation
implied that the nice value equaled the scheduling priority, which
isn't accurate.) Document that the range of nice values might
exceed -20..19. Specify what happens when you give a nice value
that is out of range, or when you don't have permissions to lower
the nice value. Bash doesn't have a builtin 'nice', so don't say
"most shells" have one.
Paul Eggert