X-Git-Url: https://git.dogcows.com/gitweb?a=blobdiff_plain;f=doc%2Ftar.texi;h=ddfa055e47e570a1c00956e3d9b3f71a62274351;hb=751b61ab25ddc03510a695d55a916943aea2f6f0;hp=480fe89b4bd88a99be0b44f0f43bfcd52702bac1;hpb=7b5e803963822e69a73d00ba62ac01b1c23f112c;p=chaz%2Ftar diff --git a/doc/tar.texi b/doc/tar.texi index 480fe89..ddfa055 100644 --- a/doc/tar.texi +++ b/doc/tar.texi @@ -646,9 +646,9 @@ If you find problems or have suggestions about this program or manual, please report them to @file{bug-tar@@gnu.org}. When reporting a bug, please be sure to include as much detail as -possible, in order to reproduce it. @FIXME{Be more specific, I'd -like to make this node as detailed as 'Bug reporting' node in Emacs -manual.} +possible, in order to reproduce it. +@FIXME{Be more specific, I'd like to make this node as detailed as +'Bug reporting' node in Emacs manual.} @node Tutorial @chapter Tutorial Introduction to @command{tar} @@ -693,8 +693,8 @@ file system. You should have some basic understanding of directory structure and how files are named according to which directory they are in. You should understand concepts such as standard output and standard input, what various definitions of the term @samp{argument} mean, and the -differences between relative and absolute file names. @FIXME{and what -else?} +differences between relative and absolute file names. +@FIXME{and what else?} @item This manual assumes that you are working from your own home directory @@ -2256,7 +2256,8 @@ respectively. The first two examples also specify a single non-option, @var{name} argument having the value @samp{archive.tar}. The last example contains only old style option letters (repeating option @samp{c} twice), not all of which are meaningful (eg., @samp{.}, -@samp{h}, or @samp{i}), with no argument value. @FIXME{not sure i liked +@samp{h}, or @samp{i}), with no argument value. +@FIXME{not sure i liked the first sentence of this paragraph..} @node All Options @@ -2791,7 +2792,7 @@ Send verbose output to @var{file} instead of to standard output. When @command{tar} is performing multi-tape backups, @var{command} is run at the end of each tape. If it exits with nonzero status, -@command{tar} fails immediately. @xref{info-script}, for a detailed +@command{tar} fails immediately. @xref{info-script}, for a detailed discussion of this feature. @opsummary{interactive} @@ -3250,7 +3251,7 @@ $ @kbd{tar --show-defaults} @noindent Notice, that this option outputs only one line. The example output -above has been split to fit page boundaries. +above has been split to fit page boundaries. @xref{defaults}. @opsummary{show-omitted-dirs} @item --show-omitted-dirs @@ -3258,6 +3259,13 @@ above has been split to fit page boundaries. Instructs @command{tar} to mention the directories it is skipping when operating on a @command{tar} archive. @xref{show-omitted-dirs}. +@opsummary{show-snapshot-field-ranges} +@item --show-snapshot-field-ranges + +Displays the range of values allowed by this version of @command{tar} +for each field in the snapshot file, then exits successfully. +@xref{Snapshot Files}. + @opsummary{show-transformed-names} @opsummary{show-stored-names} @item --show-transformed-names @@ -4297,7 +4305,7 @@ Any additional information is normally supplied to external commands in environment variables, specific to each particular operation. For example, the @option{--checkpoint-action=exec} option, defines the @env{TAR_ARCHIVE} variable to the name of the archive being worked -upon. You can, should the need be, use these variables in the +upon. You can, should the need be, use these variables in the command line of the external command. For example: @smallexample @@ -5631,7 +5639,7 @@ list of archive format names. These variables are defined prior to executing the command, so you can pass them as arguments, if you prefer. For example, if the command @var{proc} takes the member name and size as its arguments, then you -could do: +could do: @smallexample $ @kbd{tar -x -f archive.tar \ @@ -7119,45 +7127,6 @@ libc.a @end group @end smallexample -@noindent -@xopindex{directory, using in @option{--files-from} argument} -Notice that the option parsing algorithm used with @option{-T} is -stricter than the one used by shell. Namely, when specifying option -arguments, you should observe the following rules: - -@itemize @bullet -@item -When using short (single-letter) option form, its argument must -immediately follow the option letter, without any intervening -whitespace. For example: @code{-Cdir}. - -@item -When using long option form, the option argument must be separated -from the option by a single equal sign. No whitespace is allowed on -any side of the equal sign. For example: @code{--directory=dir}. - -@item -For both short and long option forms, the option argument can be given -on the next line after the option name, e.g.: - -@smallexample -@group ---directory -dir -@end group -@end smallexample - -@noindent -and - -@smallexample -@group --C -dir -@end group -@end smallexample -@end itemize - @opindex add-file If you happen to have a file whose name starts with @samp{-}, precede it with @option{--add-file} option to prevent it from @@ -7225,10 +7194,11 @@ $ @kbd{find . -size +800 -print0 | This example uses short options for typographic reasons, to avoid very long lines. -@GNUTAR is able to automatically detect @code{NUL}-terminated file lists, so -it is safe to use them even without the @option{--null} option. In -this case @command{tar} will print a warning and continue reading such -a file as if @option{--null} were actually given: +@GNUTAR is tries to automatically detect @code{NUL}-terminated file +lists, so in many cases it is safe to use them even without the +@option{--null} option. In this case @command{tar} will print a +warning and continue reading such a file as if @option{--null} were +actually given: @smallexample @group