| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
-> "file has not changed", which is more accurate for fifos.
|
|
all pipes, just for when standard input is a pipe and no
file operand is specified.
|
|
"readlink -f" behaviour and new canonicalize options, -e and -m.
|
|
install invocation, mv invocation, ln invocation): Add -t as a
short option for --target-directory, and -T as a short option for
--no-target-directory. Clean up relevant synopses a bit, so that
the language is similar for all.
|
|
Make sure "i.e." and "e.g." are followed by commas (the GNU style).
Put blank lines before and after every @example, prefer the
previous line to end in ":" (when not a sentence end, for consistency),
and prepend @noindent to the following line when appropriate.
In examples, use "--" arguments when needed to prevent undesired
interpretation of operands as options.
Use "file name" rather than "filename", as per the GNU coding standards.
Remove unwanted spaces before @footnote.
Use "---" when appropriate, instead of " -- ".
Use "name" (or something like that) rather than "path" or "pathname",
since the GNU coding standards don't allow "path".
Use @acronym, @command, @minus{}, @samp in a few places,
where appropriate.
(Target directory): Clarify description of example.
(fmt invocation): Give issue number for reference, and reword
for clarity.
(sort invocation): Note that xargs without -0 also mishandles
file names containing some special characters other than newline.
(Translating): Mention that \012 is not universally portable.
Use '\0' rather than '\000'.
(Squeezing): bourne -> Bourne.
Fix unportable usage of '\n' by replacing it with '[\n*]'.
(More details about version sort): Remove unnecessary indent
in examples.
(dd invocation): Use 'kill -s USR1', not 'kill -USR1', as POSIX
indicates that the former is more portable (the latter is an XSI
extension).
(shred invocation): Use @uref rather than @url, and use a more-typical
style for the date.
(kill invocation): Clarify usage; for example, "kill -s TERM -1"
isn't allowed.
(seq invocation): Reword to avoid implying that printf necessarily
fails for numbers outside the 32-bit range. Prefer separating
options from their operands.
(Opening the software toolbox): Give an online reference to
Robbins's article, and give a date. Don't imply that the
current documentation is unchanged from his article.
(Putting the tools together): Rework examples so that they don't
assume the C locale; nowadays many users now operate outside the C
locale by default. While we're at it, don't assume ASCII either.
Indent example to match actual output from GNU uniq. Remove some
unnecessary and confusing brackets from 'tr' operands. "Software
Tools in Pascal" is back in print, according to Amazon anyway.
Add references to Kernighan's online copies of examples.
|
|
than "filesystem", as POSIX prefers it with a space.
|
|
invocation, install invocation, mv invocation, ln invocation):
Likewise.
(link invocation): Explain how to rewrite link using ln now
that we have --no-target-directory.
(ln invocation): Explain that --no-target-directory subsumes
--no-dereference.
(unlink invocation): Modify wording to match new wording in
link invocation.
|
|
|
|
(false invocation, true invocation): --help and --version now
work unconditionally.
|
|
(pr invocation, unlink invocation): Document this.
|
|
|
|
how POSIXLY_CORRECT changes tr's behavior.
|
|
does with byte/character ranges.
|
|
|
|
(echo invocation): Document today's changes.
|
|
(chgrp invocation, chown invocation): Document it.
|
|
might write F before reading all the input.
|
|
|
|
that the options are in alphabetical order. Describe how -b works
more-accurately; this involves fixing some examples, too. Mention
what happens if the start field falls after an end field or after
a line end. Warn about using -k without -b, -g, -M, -n, or -t.
Add an example of how to sort IPv4 addresses and Apache Common
Log Format dates. Remove a duplicate example.
(Putting the tools together): Use separate options rather
than agglomerating them.
|
|
(cp invocation): Document -u (it was missing!) with new behavior.
|
|
|
|
and new dd options iflag= and oflag=.
(dd invocation): Document them.
|
|
|
|
|
|
|
|
(du invocation): FILE0 -> FILE.
|
|
--total (-c), not with --summarize.
|
|
|
|
|
|
Describe use of fractional seconds.
(date invocation, Options for date): Likewise.
(date invocation): Mention effect of LC_TIME.
(Options for date): Describe new --iso-8601=ns option.
|
|
in the `Date directives:: ...' menu entry. From Bob Proulx.
|
|
The following don't have `invocation' nodes: [, pinky, shasum, uptime
|
|
ls's --sort=directory option. ls doesn't accept that option, yet.
|
|
|
|
regular expressions (BRE), and add a link to grep's documentation.
|
|
back on USER.GROUP parsing regardless of POSIX version, as POSIX
1003.1-2001 allows that behavior as a compatible extension.
|
|
|
|
|
|
Document what forms integers may take, and say "integer"
consistently instead of "number". Warn about operands
that "expr" can misinterpret, and how to work around the problem.
|
|
in description of `N' pattern.
|
|
Improve wording for --quoting-style documentation.
Suggestions by Bruno Haible.
|
|
|
|
--date=DATE option; don't say otherwise. Patch from Padraig Brady.
|
|
|
|
Prompted by suggestion from Dan Jacobson.
(factor invocation): Add an example.
Update timing numbers for a more modern CPU.
|
|
Clarify first paragraph. @w{}-protect an expression.1
Use @option{--option}, rather than @code{--option}.
|
|
|
|
might not exit with status 1 on unusual platforms.
Mention chroot, env, nice, and su as having unusual exit
status patterns. Don't bother to mention true and false
since their exit status patterns are actually normal.
(sort invocation, su invocation): Mention its unusual exit
status pattern.
(chroot invocation): Simplify description of exit status 1.
Remove duplicate description of status 127.
(env invocation): Use consistent tenses; simplifiy description
of status 1.
(nice invocation): Likewise.
|
|
both be specified, with -r specifying the origin for -d.
|
