This corrects minor bobbles and gripes, mainly. You may not
want to make all of these. There are diffs for all three
main files in the manual. filutils.texi I'm not done with,
there will be more diffs for that one.
In one area I just commented two areas that need to be fixed
because they overflow when the manual is printed in @smallbook
format. Someone who Knows Better Than I should modify the
example appropriately.
I am contemplating a more major rewrite, but I'm not sure
I have the time or energy right now. It cettainly could be
made easier to use for the beginning user.
- Brian Youmans, FSF office staff
*** fileutils.old.texi Wed Jun 7 18:07:40 2000
--- fileutils.texi Wed Jun 7 18:02:32 2000
***************
*** 220,226 ****
@vindex version-control @r{Emacs variable}
This option corresponds to the Emacs variable @samp{version-control};
the values for @var{method} are the same as those used in Emacs.
! This options also accepts more descriptive names.
The valid @var{method}s are (unique abbreviations are accepted):
@table @samp
--- 221,227 ----
@vindex version-control @r{Emacs variable}
This option corresponds to the Emacs variable @samp{version-control};
the values for @var{method} are the same as those used in Emacs.
! This option also accepts more descriptive names.
The valid @var{method}s are (unique abbreviations are accepted):
@table @samp
***************
*** 404,410 ****
(namely, the target directory). This makes it nontrivial to perform some
operations, e.g., ``move all files from here to ../d/'', because
@code{mv * ../d/} might exhaust the argument space, and @code{ls | xargs ...}
! doesn't have a clean way to specify an extra, final, argument for each
invocation of the subject command. (It can be done by going through a
shell command, but that requires more human labor and brain power than
it should.)
--- 405,411 ----
(namely, the target directory). This makes it nontrivial to perform some
operations, e.g., ``move all files from here to ../d/'', because
@code{mv * ../d/} might exhaust the argument space, and @code{ls | xargs ...}
! doesn't have a clean way to specify an extra final argument for each
invocation of the subject command. (It can be done by going through a
shell command, but that requires more human labor and brain power than
it should.)
***************
*** 421,427 ****
If you use the GNU @code{find} program, you can move @emph{all}
files with this command:
!
@smallexample
find . -mindepth 1 -maxdepth 1 |xargs mv --target-directory=../d
@end smallexample
--- 422,428 ----
If you use the GNU @code{find} program, you can move @emph{all}
files with this command:
! @c the following doesn't fit in smallbook size
@smallexample
find . -mindepth 1 -maxdepth 1 |xargs mv --target-directory=../d
@end smallexample
***************
*** 430,436 ****
or if any file has a name containing a newline character.
The following example removes those limitations and requires both
GNU @code{find} and GNU @code{xargs}:
!
@smallexample
find . -mindepth 1 -maxdepth 1 -print0 \
| xargs --null --no-run-if-empty mv --target-directory=../d
--- 431,437 ----
or if any file has a name containing a newline character.
The following example removes those limitations and requires both
GNU @code{find} and GNU @code{xargs}:
! @c and neither does the following:
@smallexample
find . -mindepth 1 -maxdepth 1 -print0 \
| xargs --null --no-run-if-empty mv --target-directory=../d
***************
*** 497,503 ****
For non-option command-line arguments that are directories, by default
@code{ls} lists the contents of directories, not recursively, and
! omitting files with names beginning with @code{.}. For other non-option
arguments, by default @code{ls} lists just the file name. If no
non-option arguments are specified, @code{ls} lists the contents of the
current directory.
--- 498,504 ----
For non-option command-line arguments that are directories, by default
@code{ls} lists the contents of directories, not recursively, and
! omitting files with names beginning with @samp{.}. For other non-option
arguments, by default @code{ls} lists just the file name. If no
non-option arguments are specified, @code{ls} lists the contents of the
current directory.
***************
*** 573,581 ****
wildcard at the start of @var{pattern}. Sometimes it is useful
to give this option several times. For example,
! @example
$ ls --ignore='.??*' --ignore='.[^.]' --ignore='#*'
! @end example
The first option ignores names of length 3 or more that start with @samp{.},
the second ignores all two-character names that start with @samp{.}
--- 574,582 ----
wildcard at the start of @var{pattern}. Sometimes it is useful
to give this option several times. For example,
! @smallexample
$ ls --ignore='.??*' --ignore='.[^.]' --ignore='#*'
! @end smallexample
The first option ignores names of length 3 or more that start with @samp{.},
the second ignores all two-character names that start with @samp{.}
***************
*** 842,848 ****
@opindex --sort
@opindex version@r{, sorting option for @code{ls}}
Sort by version name and number, lowest first. It behaves like a default
! sort, excepted that each sequence of decimal digits is treated numerically
as an index/version number. (@xref{More details about version sort}.)
@item -X
--- 843,849 ----
@opindex --sort
@opindex version@r{, sorting option for @code{ls}}
Sort by version name and number, lowest first. It behaves like a default
! sort, except that each sequence of decimal digits is treated numerically
as an index/version number. (@xref{More details about version sort}.)
@item -X
***************
*** 922,935 ****
@itemize @bullet
@item none
@vindex none @r{color option}
! Do not use color at all. This is the default.
@item auto
@vindex auto @r{color option}
@cindex terminal, using color iff
! Only use color if standard output is a terminal.
@item always
@vindex always @r{color option}
! Always use color.
@end itemize
Specifying @samp{--color} and no @var{when} is equivalent to
@samp{--color=always}.
--- 923,936 ----
@itemize @bullet
@item none
@vindex none @r{color option}
! - Do not use color at all. This is the default.
@item auto
@vindex auto @r{color option}
@cindex terminal, using color iff
! - Only use color if standard output is a terminal.
@item always
@vindex always @r{color option}
! - Always use color.
@end itemize
Specifying @samp{--color} and no @var{when} is equivalent to
@samp{--color=always}.
***************
*** 1664,1670 ****
@opindex --group
@cindex group ownership of installed files, setting
Set the group ownership of installed files or directories to
! @var{group}. The default is the process's current group. @var{group}
may be either a group name or a numeric group id.
@item -m @var{mode}
--- 1665,1671 ----
@opindex --group
@cindex group ownership of installed files, setting
Set the group ownership of installed files or directories to
! @var{group}. The default is the process' current group. @var{group}
may be either a group name or a numeric group id.
@item -m @var{mode}
***************
*** 2318,2328 ****
Examples:
! @example
ln -s /some/name # creates link ./name pointing to /some/name
ln -s /some/name myname # creates link ./myname pointing to /some/name
ln -s a b .. # creates links ../a and ../b pointing to ./a and ./b
! @end example
@node mkdir invocation
--- 2319,2329 ----
Examples:
! @smallexample
ln -s /some/name # creates link ./name pointing to /some/name
ln -s /some/name myname # creates link ./myname pointing to /some/name
ln -s a b .. # creates links ../a and ../b pointing to ./a and ./b
! @end smallexample
@node mkdir invocation
***************
*** 2639,2647 ****
For example, to reflect a UID numbering change for one user's files
without an option like this, @code{root} might run
! @example
find / -owner OLDUSER -print0 | xargs -0 chown NEWUSER
! @end example
But that is dangerous because the interval between when the @code{find}
tests the existing file's owner and when the @code{chown} is actually run
--- 2640,2648 ----
For example, to reflect a UID numbering change for one user's files
without an option like this, @code{root} might run
! @smallexample
find / -owner OLDUSER -print0 | xargs -0 chown NEWUSER
! @end smallexample
But that is dangerous because the interval between when the @code{find}
tests the existing file's owner and when the @code{chown} is actually run
*** perm.old.texi Wed Jun 7 18:09:11 2000
--- perm.texi Wed Jun 7 17:56:35 2000
***************
*** 342,348 ****
gives users other than the owner of the file read permission and, if
it is a directory or if someone already had execute permission
to it, gives them execute permission; and it also denies them write
! permission to it file. It does not affect the permission that the
owner of the file has for it. The above mode is equivalent to
the two modes:
--- 342,348 ----
gives users other than the owner of the file read permission and, if
it is a directory or if someone already had execute permission
to it, gives them execute permission; and it also denies them write
! permission to the file. It does not affect the permission that the
owner of the file has for it. The above mode is equivalent to
the two modes:
*** getdate.old.texi Wed Jun 7 18:08:33 2000
--- getdate.texi Wed Jun 7 17:54:55 2000
***************
*** 44,54 ****
@menu
* General date syntax:: Common rules.
! * Calendar date item:: 19 Dec 1994.
! * Time of day item:: 9:20pm.
! * Time zone item:: EST, DST, BST, UTC, ...
! * Day of week item:: Monday and others.
! * Relative item in date strings:: next tuesday, 2 years ago.
* Pure numbers in date strings:: 19931219, 1440.
* Authors of getdate:: Bellovin, Salz, Berets, et al.
@end menu
--- 44,54 ----
@menu
* General date syntax:: Common rules.
! * Calendar date items:: 19 Dec 1994.
! * Time of day items:: 9:20pm.
! * Time zone items:: EST, DST, BST, UTC, ...
! * Day of week items:: Monday and others.
! * Relative items in date strings:: next tuesday, 2 years ago.
* Pure numbers in date strings:: 19931219, 1440.
* Authors of getdate:: Bellovin, Salz, Berets, et al.
@end menu
***************
*** 103,110 ****
zeros on numbers are ignored.
! @node Calendar date item
! @section Calendar date item
@cindex calendar date item
--- 103,110 ----
zeros on numbers are ignored.
! @node Calendar date items
! @section Calendar date items
@cindex calendar date item
***************
*** 113,125 ****
numerically or literally. All these strings specify the same calendar date:
@example
! 1972-09-24 # ISO 8601.
! 72-9-24 # Assume 19xx for 69 through 99, 20xx for 00 through 68.
! 72-09-24 # Leading zeros are ignored.
! 9/24/72 # Common U.S. writing.
24 September 1972
! 24 Sept 72 # September has a special abbreviation.
! 24 Sep 72 # Three-letter abbreviations always allowed.
Sep 24, 1972
24-sep-72
24sep72
--- 113,126 ----
numerically or literally. All these strings specify the same calendar date:
@example
! 1972-09-24 # ISO 8601.
! 72-9-24 # Assume 19xx for 69 through 99,
! # 20xx for 00 through 68.
! 72-09-24 # Leading zeros are ignored.
! 9/24/72 # Common U.S. writing.
24 September 1972
! 24 Sept 72 # September has a special abbreviation.
! 24 Sep 72 # Three-letter abbreviations always allowed.
Sep 24, 1972
24-sep-72
24sep72
***************
*** 173,180 ****
@end example
! @node Time of day item
! @section Time of day item
@cindex time of day item
--- 174,181 ----
@end example
! @node Time of day items
! @section Time of day items
@cindex time of day item
***************
*** 223,230 ****
but not both.
! @node Time zone item
! @section Time zone item
@cindex time zone item
--- 224,231 ----
but not both.
! @node Time zone items
! @section Time zone items
@cindex time zone item
***************
*** 343,350 ****
@end table
! @node Day of week item
! @section Day of week item
@cindex day of week item
--- 344,351 ----
@end table
! @node Day of week items
! @section Day of week items
@cindex day of week item
***************
*** 423,434 ****
The strings @samp{now} or @samp{today} are relative items corresponding
to zero-valued time displacement, these strings come from the fact
a zero-valued time displacement represents the current time when not
! otherwise change by previous items. They may be used to stress other
items, like in @samp{12:00 today}. The string @samp{this} also has
the meaning of a zero-valued time displacement, but is preferred in
date strings like @samp{this thursday}.
! When a relative item makes the resulting date to cross the boundary
between DST and non-DST (or vice-versa), the hour is adjusted according
to the local time.
--- 424,435 ----
The strings @samp{now} or @samp{today} are relative items corresponding
to zero-valued time displacement, these strings come from the fact
a zero-valued time displacement represents the current time when not
! otherwise changed by previous items. They may be used to stress other
items, like in @samp{12:00 today}. The string @samp{this} also has
the meaning of a zero-valued time displacement, but is preferred in
date strings like @samp{this thursday}.
! When a relative item causes the resulting date to cross the boundary
between DST and non-DST (or vice-versa), the hour is adjusted according
to the local time.
***************
*** 438,444 ****
@cindex pure numbers in date strings
! The precise intepretation of a pure decimal number is dependent of
the context in the date string.
If the decimal number is of the form @var{yyyy}@var{mm}@var{dd} and no
--- 439,445 ----
@cindex pure numbers in date strings
! The precise intepretation of a pure decimal number is dependent on
the context in the date string.
If the decimal number is of the form @var{yyyy}@var{mm}@var{dd} and no
