678 lines
23 KiB
HTML
678 lines
23 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of ZIPINFO</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>ZIPINFO</H1>
|
|
Section: User Commands (1)<BR>Updated: 20 April 2009 (v3.0)<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
zipinfo - list detailed information about a ZIP archive
|
|
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<B>zipinfo</B> [<B>-12smlvhMtTz</B>] <I>file</I>[<I>.zip</I>]
|
|
[<I>file(s)</I> ...] [<B>-x</B> <I>xfile(s)</I> ...]
|
|
<P>
|
|
|
|
<B>unzip</B> <B>-Z</B> [<B>-12smlvhMtTz</B>] <I>file</I>[<I>.zip</I>]
|
|
[<I>file(s)</I> ...] [<B>-x</B> <I>xfile(s)</I> ...]
|
|
|
|
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<I>zipinfo</I> lists technical information about files in a ZIP archive, most
|
|
commonly found on MS-DOS systems. Such information includes file access
|
|
permissions, encryption status, type of compression, version and operating
|
|
system or file system of compressing program, and the like. The default
|
|
behavior (with no options) is
|
|
to list single-line entries for each file in the archive, with header and
|
|
trailer lines providing summary information for the entire archive. The
|
|
format is a cross between Unix ``ls -l'' and ``unzip -v''
|
|
output. See
|
|
<B>DETAILED DESCRIPTION</B>
|
|
|
|
below. Note that <I>zipinfo</I> is the same program as <I>unzip</I> (under
|
|
Unix, a link to it); on some systems, however, <I>zipinfo</I> support may
|
|
have been omitted when <I>unzip</I> was compiled.
|
|
|
|
|
|
<A NAME="lbAE"> </A>
|
|
<H2>ARGUMENTS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="1"><I>file</I>[<I>.zip</I>]
|
|
|
|
<DD>
|
|
Path of the ZIP archive(s). If the file specification is a wildcard,
|
|
each matching file is processed in an order determined by the operating
|
|
system (or file system). Only the filename can be a wildcard; the path
|
|
itself cannot. Wildcard expressions are similar to Unix <I><A HREF="/cgi-bin/man/man2html?1+egrep">egrep</A></I>(1)
|
|
(regular) expressions and may contain:
|
|
<DL COMPACT><DT id="2"><DD>
|
|
<DL COMPACT>
|
|
<DT id="3">*<DD>
|
|
matches a sequence of 0 or more characters
|
|
<DT id="4">?<DD>
|
|
matches exactly 1 character
|
|
<DT id="5">[...]<DD>
|
|
matches any single character found inside the brackets; ranges are specified
|
|
by a beginning character, a hyphen, and an ending character. If an exclamation
|
|
point or a caret (`!' or `^') follows the left bracket, then the range of
|
|
characters within the brackets is complemented (that is, anything <I>except</I>
|
|
the characters inside the brackets is considered a match). To specify a
|
|
verbatim left bracket, the three-character sequence ``[[]'' has to be used.
|
|
</DL>
|
|
</DL>
|
|
|
|
<DT id="6"><DD>
|
|
(Be sure to quote any character that might otherwise be interpreted or
|
|
modified by the operating system, particularly under Unix and VMS.) If no
|
|
matches are found, the specification is assumed to be a literal filename;
|
|
and if that also fails, the suffix .zip is appended. Note that
|
|
self-extracting ZIP files are supported, as with any other ZIP archive;
|
|
just specify the .exe suffix (if any) explicitly.
|
|
<DT id="7">[<I>file(s)</I>]<DD>
|
|
An optional list of archive members to be processed, separated by spaces.
|
|
(VMS versions compiled with VMSCLI defined must delimit files with commas
|
|
instead.)
|
|
Regular expressions (wildcards) may be used to match multiple members; see
|
|
above. Again, be sure to quote expressions that would otherwise be expanded
|
|
or modified by the operating system.
|
|
<DT id="8">[<B>-x</B> <I>xfile(s)</I>]<DD>
|
|
An optional list of archive members to be excluded from processing.
|
|
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="9"><B>-1</B>
|
|
|
|
<DD>
|
|
list filenames only, one per line. This option excludes all others; headers,
|
|
trailers and zipfile comments are never printed. It is intended for use in
|
|
Unix shell scripts.
|
|
<DT id="10"><B>-2</B>
|
|
|
|
<DD>
|
|
list filenames only, one per line, but allow headers (<B>-h</B>), trailers
|
|
(<B>-t</B>) and zipfile comments (<B>-z</B>), as well. This option may be
|
|
useful in cases where the stored filenames are particularly long.
|
|
<DT id="11"><B>-s</B>
|
|
|
|
<DD>
|
|
list zipfile info in short Unix ``ls -l'' format. This is the default
|
|
behavior; see below.
|
|
<DT id="12"><B>-m</B>
|
|
|
|
<DD>
|
|
list zipfile info in medium Unix ``ls -l'' format. Identical to the
|
|
<B>-s</B> output, except that the compression factor, expressed as a
|
|
percentage, is also listed.
|
|
<DT id="13"><B>-l</B>
|
|
|
|
<DD>
|
|
list zipfile info in long Unix ``ls -l'' format. As with <B>-m</B>
|
|
except that the compressed size (in bytes) is printed instead of the
|
|
compression ratio.
|
|
<DT id="14"><B>-v</B>
|
|
|
|
<DD>
|
|
list zipfile information in verbose, multi-page format.
|
|
<DT id="15"><B>-h</B>
|
|
|
|
<DD>
|
|
list header line. The archive name, actual size (in bytes) and total number
|
|
of files is printed.
|
|
<DT id="16"><B>-M</B>
|
|
|
|
<DD>
|
|
pipe all output through an internal pager similar to the Unix <I><A HREF="/cgi-bin/man/man2html?1+more">more</A></I>(1)
|
|
command. At the end of a screenful of output, <I>zipinfo</I> pauses with a
|
|
``--More--'' prompt; the next screenful may be viewed by pressing the
|
|
Enter (Return) key or the space bar. <I>zipinfo</I> can be terminated by
|
|
pressing the ``q'' key and, on some systems, the Enter/Return key. Unlike
|
|
Unix <I><A HREF="/cgi-bin/man/man2html?1+more">more</A></I>(1), there is no forward-searching or editing capability.
|
|
Also, <I>zipinfo</I> doesn't notice if long lines wrap at the edge of the
|
|
screen, effectively resulting in the printing of two or more lines and the
|
|
likelihood that some text will scroll off the top of the screen before being
|
|
viewed. On some systems the number of available lines on the screen is not
|
|
detected, in which case <I>zipinfo</I> assumes the height is 24 lines.
|
|
<DT id="17"><B>-t</B>
|
|
|
|
<DD>
|
|
list totals for files listed or for all files. The number of files listed,
|
|
their uncompressed and compressed total sizes , and their overall compression
|
|
factor is printed; or, if only the totals line is being printed, the values
|
|
for the entire archive are given. The compressed total size does not include
|
|
the 12 additional header bytes of each encrypted entry. Note that the total
|
|
compressed (data) size will never match the actual zipfile size, since the
|
|
latter includes all of the internal zipfile headers in addition to the
|
|
compressed data.
|
|
<DT id="18"><B>-T</B>
|
|
|
|
<DD>
|
|
print the file dates and times in a sortable decimal format (yymmdd.hhmmss).
|
|
The default date format is a more standard, human-readable version with
|
|
abbreviated month names (see examples below).
|
|
<DT id="19"><B>-U</B>
|
|
|
|
<DD>
|
|
[UNICODE_SUPPORT only] modify or disable UTF-8 handling.
|
|
When UNICODE_SUPPORT is available, the option <B>-U</B> forces <I>unzip</I>
|
|
to escape all non-ASCII characters from UTF-8 coded filenames as ``#Uxxxx''.
|
|
This option is mainly provided for debugging purpose when the fairly new
|
|
UTF-8 support is suspected to mangle up extracted filenames.
|
|
<DT id="20"><DD>
|
|
The option <B>-UU</B> allows to entirely disable the recognition of UTF-8
|
|
encoded filenames. The handling of filename codings within <I>unzip</I> falls
|
|
back to the behaviour of previous versions.
|
|
<DT id="21"><B>-z</B>
|
|
|
|
<DD>
|
|
include the archive comment (if any) in the listing.
|
|
|
|
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>DETAILED DESCRIPTION</H2>
|
|
|
|
<I>zipinfo</I>
|
|
|
|
has a number of modes, and its behavior can be rather difficult to fathom
|
|
if one isn't familiar with Unix <I><A HREF="/cgi-bin/man/man2html?1+ls">ls</A></I>(1) (or even if one is). The default
|
|
behavior is to list files in the following format:
|
|
<P>
|
|
|
|
|
|
<P>
|
|
|
|
The last three fields are the modification date and time of
|
|
the file, and its name. The case of the filename is respected; thus
|
|
files that come from MS-DOS PKZIP are always capitalized. If the file
|
|
was zipped with a stored directory name, that is also displayed as part
|
|
of the filename.
|
|
<P>
|
|
|
|
The second and third fields indicate that the file was zipped under
|
|
Unix with version 1.9 of <I>zip</I>. Since it comes from Unix, the file
|
|
permissions at the beginning of the line are printed in Unix format.
|
|
The uncompressed file-size (2802 in this example) is the fourth field.
|
|
<P>
|
|
|
|
The fifth field consists of two characters, either of which may take
|
|
on several values. The first character may be either `t' or `b', indicating
|
|
that <I>zip</I> believes the file to be text or binary, respectively;
|
|
but if the file is encrypted, <I>zipinfo</I>
|
|
notes this fact by capitalizing the character (`T' or `B'). The second
|
|
character may also take on four values, depending on whether there is
|
|
an extended local header and/or an ``extra field'' associated with the
|
|
file (fully explained in PKWare's APPNOTE.TXT, but basically analogous to
|
|
pragmas in ANSI C--i.e., they provide a standard way to include non-standard
|
|
information in the archive). If neither exists, the character
|
|
will be a hyphen (`-'); if there is an extended local header but no extra
|
|
field, `l'; if the reverse, `x'; and if both exist, `X'. Thus the
|
|
file in this example is (probably) a text file, is not encrypted, and
|
|
has neither an extra field nor an extended local header associated with it.
|
|
The example below, on the other hand, is an encrypted binary file with an
|
|
extra field:
|
|
<P>
|
|
|
|
|
|
<P>
|
|
|
|
Extra fields are used for various purposes (see discussion of the <B>-v</B>
|
|
option below) including the storage of VMS file attributes, which is
|
|
presumably the case here. Note that the file attributes are listed in
|
|
VMS format. Some other possibilities for the host operating system (which
|
|
is actually a misnomer--host file system is more correct) include
|
|
OS/2 or NT with High Performance File System (HPFS), MS-DOS, OS/2 or NT
|
|
with File Allocation Table (FAT) file system, and Macintosh. These are
|
|
denoted as follows:
|
|
<P>
|
|
|
|
|
|
|
|
|
|
<P>
|
|
|
|
File attributes in the first two cases are indicated in a Unix-like format,
|
|
where the seven subfields indicate whether the file: (1) is a directory,
|
|
(2) is readable (always true), (3) is writable, (4) is executable (guessed
|
|
on the basis of the extension--<I>.exe</I>, <I>.com</I>, <I>.bat</I>, <I>.cmd</I>
|
|
and <I>.btm</I> files are assumed to be so), (5) has its archive bit set,
|
|
(6) is hidden, and (7) is a system file. Interpretation of Macintosh file
|
|
attributes is unreliable because some Macintosh archivers don't store any
|
|
attributes in the archive.
|
|
<P>
|
|
|
|
Finally, the sixth field indicates
|
|
the compression method and possible sub-method used. There are six methods
|
|
known at present: storing (no compression), reducing, shrinking, imploding,
|
|
tokenizing (never publicly released), and deflating. In addition, there are
|
|
four levels of reducing (1 through 4); four types of imploding (4K or 8K
|
|
sliding dictionary, and 2 or 3 Shannon-Fano trees); and four levels of
|
|
deflating (superfast, fast, normal, maximum compression). <I>zipinfo</I>
|
|
represents these methods and their sub-methods as follows: <I>stor</I>;
|
|
<I>re:1</I>, <I>re:2</I>, etc.; <I>shrk</I>; <I>i4:2</I>, <I>i8:3</I>, etc.;
|
|
<I>tokn</I>; and <I>defS</I>, <I>defF</I>, <I>defN</I>, and <I>defX</I>.
|
|
<P>
|
|
|
|
The medium and long listings are almost identical to the short format except
|
|
that they add information on the file's compression. The medium format lists
|
|
the file's compression factor as a percentage indicating the amount of space
|
|
that has been ``removed'':
|
|
<P>
|
|
|
|
|
|
<P>
|
|
|
|
In this example, the file has been compressed by more than a factor of
|
|
five; the compressed data are only 19% of the original size. The long
|
|
format gives the compressed file's size in bytes, instead:
|
|
<P>
|
|
|
|
|
|
<P>
|
|
|
|
In contrast to the <I>unzip</I> listings, the compressed size figures in
|
|
this listing format denote the complete size of compressed data, including
|
|
the 12 extra header bytes in case of encrypted entries.
|
|
<P>
|
|
|
|
Adding the <B>-T</B> option changes the file date and time to decimal
|
|
format:
|
|
<P>
|
|
|
|
|
|
<P>
|
|
|
|
Note that because of limitations in the MS-DOS format used to store file
|
|
times, the seconds field is always rounded to the nearest even second.
|
|
For Unix files this is expected to change in the next major releases of
|
|
<I><A HREF="/cgi-bin/man/man2html?1+zip">zip</A></I>(1) and <I>unzip</I>.
|
|
<P>
|
|
|
|
In addition to individual file information, a default zipfile listing
|
|
also includes header and trailer lines:
|
|
<P>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<P>
|
|
|
|
The header line gives the name of the archive, its total size, and the
|
|
total number of files; the trailer gives the number of files listed,
|
|
their total uncompressed size, and their total compressed size (not
|
|
including any of <I>zip</I>'s internal overhead). If, however, one or
|
|
more <I>file(s)</I> are provided, the header and trailer lines are
|
|
not listed. This behavior is also similar to that of Unix's ``ls -l'';
|
|
it may be overridden by specifying the <B>-h</B> and <B>-t</B> options
|
|
explicitly.
|
|
In such a case the listing format must also be specified explicitly,
|
|
since <B>-h</B> or <B>-t</B> (or both) in the absence of other options implies
|
|
that ONLY the header or trailer line (or both) is listed. See the
|
|
<B>EXAMPLES</B> section below for a semi-intelligible translation of this
|
|
nonsense.
|
|
<P>
|
|
|
|
The verbose listing is mostly self-explanatory. It also lists file
|
|
comments and the zipfile comment, if any, and the type and number of bytes
|
|
in any stored extra fields. Currently known types of extra fields include
|
|
PKWARE's authentication (``AV'') info; OS/2 extended attributes; VMS
|
|
filesystem info, both PKWARE and Info-ZIP versions; Macintosh resource
|
|
forks; Acorn/Archimedes SparkFS info; and so on. (Note
|
|
that in the case of OS/2 extended attributes--perhaps the most common
|
|
use of zipfile extra fields--the size of the stored EAs as reported by
|
|
<I>zipinfo</I> may not match the number given by OS/2's <I>dir</I> command:
|
|
OS/2 always reports the number of bytes required in 16-bit format, whereas
|
|
<I>zipinfo</I> always reports the 32-bit storage.)
|
|
<P>
|
|
|
|
Again, the compressed size figures of the individual entries include the
|
|
12 extra header bytes for encrypted entries. In contrast, the archive total
|
|
compressed size and the average compression ratio shown in the summary
|
|
bottom line are calculated <B>without</B> the extra 12 header bytes of
|
|
encrypted entries.
|
|
|
|
|
|
<A NAME="lbAH"> </A>
|
|
<H2>ENVIRONMENT OPTIONS</H2>
|
|
|
|
Modifying <I>zipinfo</I>'s default behavior via options placed in
|
|
an environment variable can be a bit complicated to explain, due to
|
|
<I>zipinfo</I>'s attempts to handle various defaults in an intuitive,
|
|
yet Unix-like, manner. (Try not to laugh.) Nevertheless, there is some
|
|
underlying logic. In brief,
|
|
there are three ``priority levels'' of options: the default options;
|
|
environment options, which can override or add to the defaults; and
|
|
explicit options given by the user, which can override or add to
|
|
either of the above.
|
|
<P>
|
|
|
|
The default listing format, as noted above, corresponds roughly
|
|
to the "zipinfo -hst" command (except when individual zipfile members
|
|
are specified).
|
|
A user who prefers the long-listing format (<B>-l</B>) can make use of the
|
|
<I>zipinfo</I>'s environment variable to change this default:
|
|
<DL COMPACT>
|
|
<DT id="22">Unix Bourne shell:<DD>
|
|
<TT>ZIPINFO=-l; export ZIPINFO</TT>
|
|
<DT id="23">Unix C shell:<DD>
|
|
<TT>setenv ZIPINFO -l</TT>
|
|
<DT id="24">OS/2 or MS-DOS:<DD>
|
|
<TT>set ZIPINFO=-l</TT>
|
|
<DT id="25">VMS (quotes for <I>lowercase</I>):<DD>
|
|
<TT>define ZIPINFO_OPTS "-l"</TT>
|
|
|
|
|
|
|
|
|
|
|
|
</DL>
|
|
<P>
|
|
|
|
If, in addition, the user dislikes the trailer line, <I>zipinfo</I>'s
|
|
concept of ``negative options'' may be used to override the default
|
|
inclusion of the line. This is accomplished by preceding the undesired
|
|
option with one or more minuses: e.g., ``-l-t'' or ``--tl'',
|
|
in this example. The first hyphen is the regular switch character, but the
|
|
one before the `t' is a minus sign. The dual use of hyphens may seem a
|
|
little awkward, but it's reasonably intuitive nonetheless: simply ignore
|
|
the first hyphen and go from there. It is also consistent with the behavior
|
|
of the Unix command <I><A HREF="/cgi-bin/man/man2html?1+nice">nice</A></I>(1).
|
|
<P>
|
|
|
|
As suggested above, the default variable names are ZIPINFO_OPTS for VMS
|
|
(where the symbol used to install <I>zipinfo</I> as a foreign command
|
|
would otherwise be confused with the environment variable), and ZIPINFO
|
|
for all other operating systems. For compatibility with <I><A HREF="/cgi-bin/man/man2html?1+zip">zip</A></I>(1),
|
|
ZIPINFOOPT is also accepted (don't ask). If both ZIPINFO and ZIPINFOOPT
|
|
are defined, however, ZIPINFO takes precedence. <I>unzip</I>'s diagnostic
|
|
option (<B>-v</B> with no zipfile name) can be used to check the values
|
|
of all four possible <I>unzip</I> and <I>zipinfo</I> environment variables.
|
|
|
|
|
|
<A NAME="lbAI"> </A>
|
|
<H2>EXAMPLES</H2>
|
|
|
|
To get a basic, short-format listing of the complete contents of a ZIP
|
|
archive <I>storage.zip</I>, with both header and totals lines, use only
|
|
the archive name as an argument to zipinfo:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo storage
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
To produce a basic, long-format listing (not verbose), including header and
|
|
totals lines, use <B>-l</B>:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo -l storage
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
To list the complete contents of the archive without header and totals
|
|
lines, either negate the <B>-h</B> and <B>-t</B> options or else specify the
|
|
contents explicitly:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo --h-t storage
|
|
zipinfo storage \*
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
(where the backslash is required only if the shell would otherwise expand
|
|
the `*' wildcard, as in Unix when globbing is turned on--double quotes around
|
|
the asterisk would have worked as well). To turn off the totals line by
|
|
default, use the environment variable (C shell is assumed here):
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
setenv ZIPINFO --t
|
|
zipinfo storage
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
To get the full, short-format listing of the first example again, given
|
|
that the environment variable is set as in the previous example, it is
|
|
necessary to specify the <B>-s</B> option explicitly, since the <B>-t</B>
|
|
option by itself implies that ONLY the footer line is to be printed:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
setenv ZIPINFO --t
|
|
zipinfo -t storage [only totals line]
|
|
zipinfo -st storage [full listing]
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
The <B>-s</B> option, like <B>-m</B> and <B>-l</B>, includes headers and
|
|
footers by default, unless otherwise specified. Since the environment
|
|
variable specified no footers and that has a higher precedence than the
|
|
default behavior of <B>-s</B>, an explicit <B>-t</B> option was necessary
|
|
to produce the full listing. Nothing was indicated about the header,
|
|
however, so the <B>-s</B> option was sufficient. Note that both the
|
|
<B>-h</B> and <B>-t</B> options, when used by themselves or with
|
|
each other, override any default listing of member files; only the header
|
|
and/or footer are printed. This behavior is useful when <I>zipinfo</I> is
|
|
used with a wildcard zipfile specification; the contents of all zipfiles
|
|
are then summarized with a single command.
|
|
<P>
|
|
|
|
To list information on a single file within the archive, in medium format,
|
|
specify the filename explicitly:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo -m storage unshrink.c
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
The specification of any member file, as in this example, will override
|
|
the default header and totals lines; only the single line of information
|
|
about the requested file will be printed. This is intuitively what one
|
|
would expect when requesting information about a single file. For multiple
|
|
files, it is often useful to know the total compressed and uncompressed
|
|
size; in such cases <B>-t</B> may be specified explicitly:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo -mt storage "*.[ch]" Mak\*
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
To get maximal information about the ZIP archive, use the verbose
|
|
option. It is usually wise to pipe the output into a filter such as
|
|
Unix <I><A HREF="/cgi-bin/man/man2html?1+more">more</A></I>(1) if the operating system allows it:
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo -v storage | more
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
Finally, to see the most recently modified files in the archive, use
|
|
the <B>-T</B> option in conjunction with an external sorting utility
|
|
such as Unix <I><A HREF="/cgi-bin/man/man2html?1+sort">sort</A></I>(1) (and <I><A HREF="/cgi-bin/man/man2html?1+sed">sed</A></I>(1) as well, in this example):
|
|
<P>
|
|
|
|
|
|
|
|
<PRE>
|
|
zipinfo -T storage | sort -nr -k 7 | sed 15q
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
<P>
|
|
|
|
The <B>-nr</B> option to <I><A HREF="/cgi-bin/man/man2html?1+sort">sort</A></I>(1) tells it to sort numerically
|
|
in reverse order rather than in textual order, and the <B>-k 7</B> option
|
|
tells it to sort on the seventh field. This
|
|
assumes the default short-listing format; if <B>-m</B> or <B>-l</B> is
|
|
used, the proper <I><A HREF="/cgi-bin/man/man2html?1+sort">sort</A></I>(1) option would be <B>-k 8</B>.
|
|
Older versions of <I><A HREF="/cgi-bin/man/man2html?1+sort">sort</A></I>(1) do not support the <B>-k</B> option,
|
|
but you can use the traditional <B>+</B> option instead, e.g.,
|
|
<B>+6</B> instead of <B>-k 7</B>. The <I><A HREF="/cgi-bin/man/man2html?1+sed">sed</A></I>(1)
|
|
command filters out all but the first 15 lines of the listing. Future
|
|
releases of <I>zipinfo</I> may incorporate date/time and filename sorting
|
|
as built-in options.
|
|
|
|
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>TIPS</H2>
|
|
|
|
The author finds it convenient to define an alias <I>ii</I> for <I>zipinfo</I>
|
|
on systems that allow aliases (or, on other systems, copy/rename the
|
|
executable, create a link or create a command file with the name <I>ii</I>).
|
|
The <I>ii</I> usage parallels the common <I>ll</I> alias for long listings in
|
|
Unix, and the similarity between the outputs of the two commands was
|
|
intentional.
|
|
|
|
|
|
<A NAME="lbAK"> </A>
|
|
<H2>BUGS</H2>
|
|
|
|
As with <I>unzip</I>, <I>zipinfo</I>'s <B>-M</B> (``more'') option is overly
|
|
simplistic in its handling of screen output; as noted above, it fails to detect
|
|
the wrapping of long lines and may thereby cause lines at the top of the screen
|
|
to be scrolled off before being read. <I>zipinfo</I> should detect and treat
|
|
each occurrence of line-wrap as one additional line printed. This requires
|
|
knowledge of the screen's width as well as its height. In addition,
|
|
<I>zipinfo</I> should detect the true screen geometry on all systems.
|
|
<P>
|
|
|
|
<I>zipinfo</I>'s listing-format behavior is unnecessarily complex and should
|
|
be simplified. (This is not to say that it will be.)
|
|
<P>
|
|
|
|
|
|
<A NAME="lbAL"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<I><A HREF="/cgi-bin/man/man2html?1+ls">ls</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+funzip">funzip</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+unzip">unzip</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+unzipsfx">unzipsfx</A></I>(1),
|
|
<I><A HREF="/cgi-bin/man/man2html?1+zip">zip</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+zipcloak">zipcloak</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+zipnote">zipnote</A></I>(1), <I><A HREF="/cgi-bin/man/man2html?1+zipsplit">zipsplit</A></I>(1)
|
|
|
|
|
|
<A NAME="lbAM"> </A>
|
|
<H2>URL</H2>
|
|
|
|
The Info-ZIP home page is currently at
|
|
|
|
|
|
<PRE>
|
|
<A HREF="http://www.info-zip.org/pub/infozip/">http://www.info-zip.org/pub/infozip/</A>
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
<PRE>
|
|
<A HREF="ftp://ftp.info-zip.org/pub/infozip/">ftp://ftp.info-zip.org/pub/infozip/</A> .
|
|
|
|
</PRE>
|
|
|
|
|
|
|
|
|
|
|
|
<A NAME="lbAN"> </A>
|
|
<H2>AUTHOR</H2>
|
|
|
|
Greg ``Cave Newt'' Roelofs. ZipInfo contains pattern-matching code
|
|
by Mark Adler and fixes/improvements by many others. Please refer to the
|
|
CONTRIBS file in the UnZip source distribution for a more complete list.
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="26"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="27"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="28"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="29"><A HREF="#lbAE">ARGUMENTS</A><DD>
|
|
<DT id="30"><A HREF="#lbAF">OPTIONS</A><DD>
|
|
<DT id="31"><A HREF="#lbAG">DETAILED DESCRIPTION</A><DD>
|
|
<DT id="32"><A HREF="#lbAH">ENVIRONMENT OPTIONS</A><DD>
|
|
<DT id="33"><A HREF="#lbAI">EXAMPLES</A><DD>
|
|
<DT id="34"><A HREF="#lbAJ">TIPS</A><DD>
|
|
<DT id="35"><A HREF="#lbAK">BUGS</A><DD>
|
|
<DT id="36"><A HREF="#lbAL">SEE ALSO</A><DD>
|
|
<DT id="37"><A HREF="#lbAM">URL</A><DD>
|
|
<DT id="38"><A HREF="#lbAN">AUTHOR</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:05:31 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|