neulab/tldr huggingface dataset:
-q     perform operations quietly (-qq = even quieter).  Ordinarily unzip prints the names of the files it's extracting or testing, the extraction methods, any file or zipfile comments that may be stored in the archive, and possibly a summary when finished with each archive.  The -q[q] options suppress the printing of some or all of these messages.
-s     [OS/2, NT, MS-DOS] convert spaces in filenames to underscores. Since all PC operating systems allow spaces in filenames, unzip by default extracts filenames with spaces intact (e.g., ``EA DATA. SF'').  This can be awkward, however, since MS-DOS in particular does not gracefully support spaces in filenames. Conversion of spaces to underscores can eliminate the awkwardness in some cases.
-S     [VMS] convert text files (-a, -aa) into Stream_LF record format, instead of the text-file default, variable-length record format. (Stream_LF is the default record format of VMS unzip. It is applied unless conversion (-a, -aa and/or -b, -bb) is requested or a VMS-specific entry is processed.)
-U     [UNICODE_SUPPORT only] modify or disable UTF-8 handling.  When UNICODE_SUPPORT is available, the option -U forces unzip to escape all non-ASCII characters from UTF-8 coded filenames as ``#Uxxxx'' (for UCS-2 characters, or ``#Lxxxxxx'' for unicode codepoints needing 3 octets).  This option is mainly provided for debugging purpose when the fairly new UTF-8 support is suspected to mangle up extracted filenames.
The option -UU allows to entirely disable the recognition of UTF-8 encoded filenames.  The handling of filename codings within unzip falls back to the behaviour of previous versions.
[old, obsolete usage] leave filenames uppercase if created under MS-DOS, VMS, etc.  See -L above.
-V     retain (VMS) file version numbers.  VMS files can be stored with a version number, in the format file.ext;##.  By default the ``;##'' version numbers are stripped, but this option allows them to be retained.  (On file systems that limit filenames to particularly short lengths, the version numbers may be truncated or stripped regardless of this option.)
-W     [only when WILD_STOP_AT_DIR compile-time option enabled] modifies the pattern matching routine so that both `?' (single-char wildcard) and `*' (multi-char wildcard) do not match the directory separator character `/'.  (The two-character sequence ``**'' acts as a multi-char wildcard that includes the directory separator in its matched characters.)  Examples:
"*.c" matches "foo.c" but not "mydir/foo.c" "**.c" matches both "foo.c" and "mydir/foo.c" "*/*.c" matches "bar/foo.c" but not "baz/bar/foo.c" "??*/*" matches "ab/foo" and "abc/foo" but not "a/foo" or "a/b/foo"
This modified behaviour is equivalent to the pattern matching style used by the shells of some of UnZip's supported target OSs (one example is Acorn RISC OS).  This option may not be available on systems where the Zip archive's internal directory separator character `/' is allowed as regular character in native operating system filenames.  (Currently, UnZip uses the same pattern matching rules for both wildcard zipfile specifications and zip entry selection patterns in most ports.  For systems allowing `/' as regular filename character, the -W option would not work as expected on a wildcard zipfile specification.)
-X     [VMS, Unix, OS/2, NT, Tandem] restore owner/protection info (UICs and ACL entries) under VMS, or user and group info (UID/GID) under Unix, or access control lists (ACLs) under certain network-enabled versions of OS/2 (Warp Server with IBM LAN Server/Requester 3.0 to 5.0; Warp Connect with IBM Peer 1.0), or security ACLs under Windows NT.  In most cases this will require special system privileges, and doubling the option (-XX) under NT instructs unzip to use privileges for extraction; but under Unix, for example, a user who belongs to several groups can restore files owned by any of those groups, as long as the user IDs match his or her own. Note that ordinary file attributes are always restored--this option applies only to optional, extra ownership info available on some operating systems.  [NT's access control lists do not appear to be especially compatible with OS/2's, so no attempt is made at cross-platform portability of access privileges.  It is not clear under what conditions this would ever be useful anyway.]
-Y     [VMS] treat archived file name endings of ``.nnn'' (where ``nnn'' is a decimal  number) as if they were VMS version numbers (``;nnn'').  (The default is to treat them as file types.) Example: "a.b.3" -> "a.b;3".
-$     [MS-DOS, OS/2, NT] restore the volume label if the extraction medium is removable (e.g., a diskette).  Doubling the option (-$$) allows fixed media (hard disks) to be labelled as well.  By default, volume labels are ignored.
-/ extensions [Acorn only] overrides the extension list supplied by Unzip$Ext environment variable. During extraction, filename extensions that match one of the items in this extension list are swapped in front of the base name of the extracted file.
-:     [all but Acorn, VM/CMS, MVS, Tandem] allows to extract archive members into locations outside of the current `` extraction root folder''. For security reasons, unzip normally removes ``parent dir'' path components (``../'') from the names of extracted file. This safety feature (new for version 5.50) prevents unzip from accidentally writing files to ``sensitive'' areas outside the active extraction folder tree head.  The -: option lets unzip switch back to its previous, more liberal behaviour, to allow exact extraction of (older) archives that used ``../'' components to create multiple directory trees at the level of the current extraction folder.  This option does not enable writing explicitly to the root directory (``/'').  To achieve this, it is necessary to set the extraction target folder to root (e.g. -d / ). However, when the -: option is specified, it is still possible to implicitly write to the root directory by specifying enough ``../'' path components within the zip archive.  Use this option with extreme caution.
-^     [Unix only] allow control characters in names of extracted ZIP archive entries.  On Unix, a file name may contain any (8-bit) character code with the two exception '/' (directory delimiter) and NUL (0x00, the C string termination indicator), unless the specific file system has more restrictive conventions.  Generally, this allows to embed ASCII control characters (or even sophisticated control sequences) in file names, at least on 'native' Unix file systems.  However, it may be highly suspicious to make use of this Unix "feature".  Embedded control characters in file names might have nasty side effects when displayed on screen by some listing code without sufficient filtering.  And, for ordinary users, it may be difficult to handle such file names (e.g. when trying to specify it for open, copy, move, or delete operations).  Therefore, unzip applies a filter by default that removes potentially dangerous control characters from the extracted file names. The -^ option allows to override this filter in the rare case that embedded filename control characters are to be intentionally restored.
-2     [VMS] force unconditionally conversion of file names to ODS2-compatible names.  The default is to exploit the destination file system, preserving case and extended file name characters on an ODS5 destination file system; and applying the ODS2-compatibility file name filtering on an ODS2 destination file system.
unzip's default behavior may be modified via options placed in an environment variable.  This can be done with any option, but it is probably most useful with the -a, -L, -C, -q, -o, or -n modifiers:  make unzip auto-convert text files by default, make it convert filenames from uppercase systems to lowercase, make it match names case-insensitively, make it quieter, or make it always overwrite or never overwrite files as it extracts them.  For example, to make unzip act as quietly as possible, only reporting errors, one would use one of the following commands:
Unix Bourne shell: UNZIP=-qq; export UNZIP
Unix C shell: setenv UNZIP -qq
OS/2 or MS-DOS: set UNZIP=-qq
VMS (quotes for lowercase): define UNZIP_OPTS "-qq"
Environment options are, in effect, considered to be just like any other command-line options, except that they are effectively the first options on the command line.  To override an environment option, one may use the ``minus operator'' to remove it.  For instance, to override one of the quiet-flags in the example above, use the command
unzip --q[other options] zipfile
The first hyphen is the normal switch character, and the second is a minus sign, acting on the q option.  Thus the effect here is to cancel one quantum of quietness.  To cancel both quiet flags, two (or more) minuses may be used:
unzip -t--q zipfile unzip ---qt zipfile
(the two are equivalent).  This may seem awkward or confusing, but it is reasonably intuitive:  just ignore the first hyphen and go from there. It is also consistent with the behavior of Unix nice(1).
As suggested by the examples above, the default variable names are UNZIP_OPTS for VMS (where the symbol used to install unzip as a foreign command would otherwise be confused with the environment variable), and UNZIP for all other operating systems.  For compatibility with zip(1L), UNZIPOPT is also accepted (don't ask).  If both UNZIP and UNZIPOPT are defined, however, UNZIP takes precedence.  unzip's diagnostic option (-v with no zipfile name) can be used to check the values of all four possible unzip and zipinfo environment variables.
The timezone variable (TZ) should be set according to the local timezone in order for the -f and -u to operate correctly.  See the description of -f above for details.  This variable may also be necessary to get timestamps of extracted files to be set correctly.  The WIN32 (Win9x/ME/NT4/2K/XP/2K3) port of unzip gets the timezone configuration from the registry, assuming it is correctly set in the Control Panel. The TZ variable is ignored for this port.
Encrypted archives are fully supported by Info-ZIP software, but due to United States export restrictions, de-/encryption support might be disabled in your compiled binary.  However, since spring 2000, US export restrictions have been liberated, and our source archives do now include full crypt code.  In case you need binary distributions with crypt support enabled, see the file ``WHERE'' in any Info-ZIP source or binary distribution for locations both inside and outside the US.
Some compiled versions of unzip may not support decryption.  To check a version for crypt support, either attempt to test or extract an encrypted archive, or else check unzip's diagnostic screen (see the -v option above) for ``[decryption]'' as one of the special compilation options.
As noted above, the -P option may be used to supply a password on the command line, but at a cost in security.  The preferred decryption method is simply to extract normally; if a zipfile member is encrypted, unzip will prompt for the password without echoing what is typed.  unzip continues to use the same password as long as it appears to be valid, by testing a 12-byte header on each file.  The correct password will always check out against the header, but there is a 1-in-256 chance that an incorrect password will as well.  (This is a security feature of the PKWARE zipfile format; it helps prevent brute-force attacks that might otherwise gain a large speed advantage by testing only the header.)  In the case that an incorrect password is given but it passes the header test anyway, either an incorrect CRC will be generated for the extracted data or else unzip will fail during the extraction because the ``decrypted'' bytes do not constitute a valid compressed data stream.
If the first password fails the header check on some file, unzip will prompt for another password, and so on until all files are extracted.  If a password is not known, entering a null password (that is, just a carriage return or ``Enter'') is taken as a signal to skip all further prompting.  Only unencrypted files in the archive(s) will thereafter be extracted.  (In fact, that's not quite true; older versions of zip(1L) and zipcloak(1L) allowed null passwords, so unzip checks each encrypted file to see if the null password works.  This may result in ``false positives'' and extraction errors, as noted above.)
Archives encrypted with 8-bit passwords (for example, passwords with accented European characters) may not be portable across systems and/or other archivers.  This problem stems from the use of multiple encoding methods for such characters, including Latin-1 (ISO 8859-1) and OEM code page 850.  DOS PKZIP 2.04g uses the OEM code page; Windows PKZIP 2.50 uses Latin-1 (and is therefore incompatible with DOS PKZIP); Info-ZIP uses the OEM code page on DOS, OS/2 and Win3.x ports but ISO coding (Latin-1 etc.) everywhere else; and Nico Mak's WinZip 6.x does not allow 8-bit passwords at all.  UnZip 5.3 (or newer) attempts to use the default character set first (e.g., Latin-1), followed by the alternate one (e.g., OEM code page) to test passwords.  On EBCDIC systems, if both of these fail, EBCDIC encoding will be tested as a last resort.  (EBCDIC is not tested on non-EBCDIC systems, because there are no known archivers that encrypt using EBCDIC encoding.)  ISO character encodings other than Latin-1 are not supported.  The new addition of (partially) Unicode (resp.  UTF-8) support in UnZip 6.0 has not yet been adapted to the encryption password handling in unzip.  On systems that use UTF-8 as native character encoding, unzip simply tries decryption with the native UTF-8 encoded password; the built-in attempts to check the password in translated encoding have not yet been adapted for UTF-8 support and will consequently fail.
To use unzip to extract all members of the archive letters.zip into the current directory and subdirectories below it, creating any subdirectories as necessary:
unzip letters
To extract all members of letters.zip into the current directory only:
unzip -j letters
To test letters.zip, printing only a summary message indicating whether the archive is OK or not:
unzip -tq letters
To test all zipfiles in the current directory, printing only the summaries:
unzip -tq \*.zip
(The backslash before the asterisk is only required if the shell expands wildcards, as in Unix; double quotes could have been used instead, as in the source examples below.)  To extract to standard output all members of letters.zip whose names end in .tex, auto-converting to the local end-of- line convention and piping the output into more(1):
unzip -ca letters \*.tex | more
To extract the binary file paper1.dvi to standard output and pipe it to a printing program:
unzip -p articles paper1.dvi | dvips
To extract all FORTRAN and C source files--*.f, *.c, *.h, and Makefile--into the /tmp directory:
unzip source.zip "*.[fch]" Makefile -d /tmp
(the double quotes are necessary only in Unix and only if globbing is turned on).  To extract all FORTRAN and C source files, regardless of case (e.g., both *.c and *.C, and any makefile, Makefile, MAKEFILE or similar):
unzip -C source.zip "*.[fch]" makefile -d /tmp
To extract any such files but convert any uppercase MS-DOS or VMS names to lowercase and convert the line-endings of all of the files to the local standard (without respect to any files that might be marked ``binary''):
unzip -aaCL source.zip "*.[fch]" makefile -d /tmp
To extract only newer versions of the files already in the current directory, without querying (NOTE:  be careful of unzipping in one timezone a zipfile created in another--ZIP archives other than those created by Zip 2.1 or later contain no timezone information, and a ``newer'' file from an eastern timezone may, in fact, be older):
unzip -fo sources
To extract newer versions of the files already in the current directory and to create any files not already there (same caveat as previous example):
unzip -uo sources
To display a diagnostic screen showing which unzip and zipinfo options are stored in environment variables, whether decryption support was compiled in, the compiler with which unzip was compiled, etc.:
unzip -v
In the last five examples, assume that UNZIP or UNZIP_OPTS is set to -q. To do a singly quiet listing:
unzip -l file.zip
To do a doubly quiet listing:
unzip -ql file.zip
(Note that the ``.zip'' is generally not necessary.)  To do a standard listing:
unzip --ql file.zip or unzip -l-q file.zip or unzip -l--q file.zip (Extra minuses in options don't hurt.)
The current maintainer, being a lazy sort, finds it very useful to define a pair of aliases:  tt for ``unzip -tq'' and ii for ``unzip -Z'' (or ``zipinfo'').  One may then simply type ``tt zipfile'' to test an archive, something that is worth making a habit of doing.  With luck unzip will report ``No errors detected in compressed data of zipfile.zip,'' after which one may breathe a sigh of relief.
The maintainer also finds it useful to set the UNZIP environment variable to ``-aL'' and is tempted to add ``-C'' as well.  His ZIPINFO variable is set to ``-z''.
1      one or more warning errors were encountered, but processing completed successfully anyway.  This includes zipfiles where one or more files was skipped due to unsupported compression method or encryption with an unknown password.
2      a generic error in the zipfile format was detected. Processing may have completed successfully anyway; some broken zipfiles created by other archivers have simple work-arounds.
3      a severe error in the zipfile format was detected. Processing probably failed immediately.
4      unzip was unable to allocate memory for one or more buffers during program initialization.
5      unzip was unable to allocate memory or unable to obtain a tty to read the decryption password(s).
6      unzip was unable to allocate memory during decompression to disk.
7      unzip was unable to allocate memory during in-memory decompression.
8      [currently not used]
9      the specified zipfiles were not found.
10     invalid options were specified on the command line.
11     no matching files were found.
12     invalid zip file with overlapped components (possible zip bomb).
50     the disk is (or was) full during extraction.
51     the end of the ZIP archive was encountered prematurely.
80     the user aborted unzip prematurely with control-C (or similar)
81     testing or extraction of one or more files failed due to unsupported compression methods or unsupported decryption.
82     no files were found due to bad decryption password(s).  (If even one file is successfully processed, however, the exit status is 1.)
VMS interprets standard Unix (or PC) return values as other, scarier- looking things, so unzip instead maps them into VMS-style status codes. The current mapping is as follows:   1 (success) for normal exit, 0x7fff0001 for warning errors, and (0x7fff000? + 16*normal_unzip_exit_status) for all other errors, where the `?' is 2 (error) for unzip values 2, 9-11 and 80-82, and 4 (fatal error) for the remaining ones (3-8, 50, 51).  In addition, there is a compilation option to expand upon this behavior:  defining RETURN_CODES results in a human- readable explanation of what the error status means.
Multi-part archives are not yet supported, except in conjunction with zip.  (All parts must be concatenated together in order, and then ``zip -F'' (for zip 2.x) or ``zip -FF'' (for zip 3.x) must be performed on the concatenated archive in order to ``fix'' it.  Also, zip 3.0 and later can combine multi-part (split) archives into a combined single-file archive using ``zip -s- inarchive -O outarchive''.  See the zip 3 manual page for more information.)  This will definitely be corrected in the next major release.
Archives read from standard input are not yet supported, except with funzip (and then only the first member of the archive can be extracted).
Archives encrypted with 8-bit passwords (e.g., passwords with accented European characters) may not be portable across systems and/or other archivers.  See the discussion in DECRYPTION above.
unzip's -M (``more'') option tries to take into account automatic wrapping of long lines. However, the code may fail to detect the correct wrapping locations. First, TAB characters (and similar control sequences) are not taken into account, they are handled as ordinary printable characters.  Second, depending on the actual system / OS port, unzip may not detect the true screen geometry but rather rely on "commonly used" default dimensions.  The correct handling of tabs would require the implementation of a query for the actual tabulator setup on the output console.
Dates, times and permissions of stored directories are not restored except under Unix. (On Windows NT and successors, timestamps are now restored.)
[MS-DOS] When extracting or testing files from an archive on a defective floppy diskette, if the ``Fail'' option is chosen from DOS's ``Abort, Retry, Fail?'' message, older versions of unzip may hang the system, requiring a reboot.  This problem appears to be fixed, but control-C (or control-Break) can still be used to terminate unzip.
Under DEC Ultrix, unzip would sometimes fail on long zipfiles (bad CRC, not always reproducible).  This was apparently due either to a hardware bug (cache memory) or an operating system bug (improper handling of page faults?).  Since Ultrix has been abandoned in favor of Digital Unix (OSF/1), this may not be an issue anymore.
[Unix] Unix special files such as FIFO buffers (named pipes), block devices and character devices are not restored even if they are somehow represented in the zipfile, nor are hard-linked files relinked. Basically the only file types restored by unzip are regular files, directories and symbolic (soft) links.
[OS/2] Extended attributes for existing directories are only updated if the -o (``overwrite all'') option is given.  This is a limitation of the operating system; because directories only have a creation time associated with them, unzip has no way to determine whether the stored attributes are newer or older than those on disk.  In practice this may mean a two-pass approach is required:  first unpack the archive normally (with or without freshening/updating existing files), then overwrite just the directory entries (e.g., ``unzip -o foo */'').
[VMS] When extracting to another directory, only the [.foo] syntax is accepted for the -d option; the simple Unix foo syntax is silently ignored (as is the less common VMS foo.dir syntax).
[VMS] When the file being extracted already exists, unzip's query only allows skipping, overwriting or renaming; there should additionally be a choice for creating a new version of the file.  In fact, the ``overwrite'' choice does create a new version; the old version is not overwritten or deleted.
funzip(1L), zip(1L), zipcloak(1L), zipgrep(1L), zipinfo(1L), zipnote(1L), zipsplit(1L)
The Info-ZIP home page is currently at http://www.info-zip.org/pub/infozip/ or ftp://ftp.info-zip.org/pub/infozip/ .
The primary Info-ZIP authors (current semi-active members of the Zip-Bugs workgroup) are:  Ed Gordon (Zip, general maintenance, shared code, Zip64, Win32, Unix, Unicode); Christian Spieler (UnZip maintenance coordination, VMS, MS-DOS, Win32, shared code, general Zip and UnZip integration and optimization); Onno van der Linden (Zip); Mike White (Win32, Windows GUI, Windows DLLs); Kai Uwe Rommel (OS/2, Win32); Steven M. Schweda (VMS, Unix, support of new features); Paul Kienitz (Amiga, Win32, Unicode); Chris Herborth (BeOS, QNX, Atari); Jonathan Hudson (SMS/QDOS); Sergio Monesi (Acorn RISC OS); Harald Denker (Atari, MVS); John Bush (Solaris, Amiga); Hunter Goatley (VMS, Info-ZIP Site maintenance); Steve Salisbury (Win32); Steve Miller (Windows CE GUI), Johnny Lee (MS-DOS, Win32, Zip64); and Dave Smith (Tandem NSK).
The following people were former members of the Info-ZIP development group and provided major contributions to key parts of the current code: Greg ``Cave Newt'' Roelofs (UnZip, unshrink decompression); Jean-loup Gailly (deflate compression); Mark Adler (inflate decompression, fUnZip).
The author of the original unzip code upon which Info-ZIP's was based is Samuel H. Smith; Carl Mascott did the first Unix port; and David P. Kirschbaum organized and led Info-ZIP in its early days with Keith Petersen hosting the original mailing list at WSMR-SimTel20.  The full list of contributors to UnZip has grown quite large; please refer to the CONTRIBS file in the UnZip source distribution for a relatively complete version.
v1.2   15 Mar 89   Samuel H. Smith v2.0    9 Sep 89   Samuel H. Smith v2.x   fall 1989   many Usenet contributors v3.0    1 May 90   Info-ZIP (DPK, consolidator) v3.1   15 Aug 90   Info-ZIP (DPK, consolidator) v4.0    1 Dec 90   Info-ZIP (GRR, maintainer) v4.1   12 May 91   Info-ZIP v4.2   20 Mar 92   Info-ZIP (Zip-Bugs subgroup, GRR) v5.0   21 Aug 92   Info-ZIP (Zip-Bugs subgroup, GRR) v5.01  15 Jan 93   Info-ZIP (Zip-Bugs subgroup, GRR) v5.1    7 Feb 94   Info-ZIP (Zip-Bugs subgroup, GRR) v5.11   2 Aug 94   Info-ZIP (Zip-Bugs subgroup, GRR) v5.12  28 Aug 94   Info-ZIP (Zip-Bugs subgroup, GRR) v5.2   30 Apr 96   Info-ZIP (Zip-Bugs subgroup, GRR) v5.3   22 Apr 97   Info-ZIP (Zip-Bugs subgroup, GRR) v5.31  31 May 97   Info-ZIP (Zip-Bugs subgroup, GRR) v5.32   3 Nov 97   Info-ZIP (Zip-Bugs subgroup, GRR) v5.4   28 Nov 98   Info-ZIP (Zip-Bugs subgroup, SPC) v5.41  16 Apr 00   Info-ZIP (Zip-Bugs subgroup, SPC) v5.42  14 Jan 01   Info-ZIP (Zip-Bugs subgroup, SPC) v5.5   17 Feb 02   Info-ZIP (Zip-Bugs subgroup, SPC) v5.51  22 May 04   Info-ZIP (Zip-Bugs subgroup, SPC) v5.52  28 Feb 05   Info-ZIP (Zip-Bugs subgroup, SPC) v6.0   20 Apr 09   Info-ZIP (Zip-Bugs subgroup, SPC)
CSVSTAT(1)                           csvkit                           CSVSTAT(1)
csvstat - csvstat Documentation
Prints descriptive statistics for all columns in a CSV file. Will intelligently determine the type of each column and then print analysis relevant to that type (ranges for dates, mean and median for integers, etc.):
usage: csvstat [-h] [-d DELIMITER] [-t] [-q QUOTECHAR] [-u {0,1,2,3}] [-b] [-p ESCAPECHAR] [-z FIELD_SIZE_LIMIT] [-e ENCODING] [-S] [-H] [-K SKIP_LINES] [-v] [-l] [--zero] [-V] [--csv] [-n] [-c COLUMNS] [--type] [--nulls] [--unique] [--min] [--max] [--sum] [--mean] [--median] [--stdev] [--len] [--freq] [--freq-count FREQ_COUNT] [--count] [-y SNIFF_LIMIT] [FILE]
Print descriptive statistics for each column in a CSV file.
optional arguments: -h, --help            show this help message and exit --csv                 Output results as a CSV, rather than text. -n, --names           Display column names and indices from the input CSV and exit. -c COLUMNS, --columns COLUMNS A comma separated list of column indices, names or ranges to be examined, e.g. "1,id,3-5". Defaults to all columns. --type                Only output data type. --nulls               Only output whether columns contains nulls. --unique              Only output counts of unique values. --min                 Only output smallest values. --max                 Only output largest values. --sum                 Only output sums. --mean                Only output means. --median              Only output medians. --stdev               Only output standard deviations. --len                 Only output the length of the longest values. --freq                Only output lists of frequent values. --freq-count FREQ_COUNT The maximum number of frequent values to display. --count               Only output total row count. -y SNIFF_LIMIT, --snifflimit SNIFF_LIMIT Limit CSV dialect sniffing to the specified number of bytes. Specify "0" to disable sniffing entirely.
csvstat examples/realdata/FY09_EDU_Recipients_by_State.csv
When an statistic name is passed, only that stat will be printed:
csvstat --min examples/realdata/FY09_EDU_Recipients_by_State.csv
1. State Name: None 2. State Abbreviate: None 3. Code: 1 4. Montgomery GI Bill-Active Duty: 435 5. Montgomery GI Bill- Selective Reserve: 48 6. Dependents' Educational Assistance: 118 7. Reserve Educational Assistance Program: 60 8. Post-Vietnam Era Veteran's Educational Assistance Program: 1 9. TOTAL: 768 10. j: None
If a single stat and a single column are requested, only a value will be returned:
csvstat -c 4 --mean examples/realdata/FY09_EDU_Recipients_by_State.csv
6,263.904
GIT-VAR(1)                         Git Manual                         GIT-VAR(1)
git-var - Show a Git logical variable
git var ( -l | <variable> )
Prints a Git logical variable.
-l Cause the logical variables to be listed. In addition, all the variables of the Git configuration file .git/config are listed as well. (However, the configuration variables listing functionality is deprecated in favor of git config -l.)
$ git var GIT_AUTHOR_IDENT Eric W. Biederman <ebiederm@lnxi.com> 1121223278 -0600
GIT_AUTHOR_IDENT The author of a piece of code.
GIT_COMMITTER_IDENT The person who put a piece of code into Git.
GIT_EDITOR Text editor for use by Git commands. The value is meant to be interpreted by the shell when it is used. Examples: ~/bin/vi, $SOME_ENVIRONMENT_VARIABLE, "C:\Program Files\Vim\gvim.exe" --nofork. The order of preference is the $GIT_EDITOR environment variable, then core.editor configuration, then $VISUAL, then $EDITOR, and then the default chosen at compile time, which is usually vi.
GIT_PAGER Text viewer for use by Git commands (e.g., less). The value is meant to be interpreted by the shell. The order of preference is the $GIT_PAGER environment variable, then core.pager configuration, then $PAGER, and then the default chosen at compile time (usually less).
git-commit-tree(1) git-tag(1) git-config(1)
DMIDECODE(8)                 System Manager's Manual                DMIDECODE(8)
dmidecode - DMI table decoder
dmidecode [OPTIONS]
dmidecode is a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format. This table contains a description of the system's hardware components, as well as other useful pieces of information such as serial numbers and BIOS revision. Thanks to this table, you can retrieve this information without having to probe for the actual hardware.  While this is a good point in terms of report speed and safeness, this also makes the presented information possibly unreliable.
The DMI table doesn't only describe what the system is currently made of, it also can report the possible evolutions (such as the fastest supported CPU or the maximal amount of memory supported).
SMBIOS stands for System Management BIOS, while DMI stands for Desktop Management Interface. Both standards are tightly related and developed by the DMTF (Desktop Management Task Force).
As you run it, dmidecode will try to locate the DMI table. It will first try to read the DMI table from sysfs, and next try reading directly from memory if sysfs access failed.  If dmidecode succeeds in locating a valid DMI table, it will then parse this table and display a list of records like this one:
Handle 0x0002, DMI type 2, 8 bytes.  Base Board Information Manufacturer: Intel Product Name: C440GX+ Version: 727281-001 Serial Number: INCY92700942
Each record has:
• A handle. This is a unique identifier, which allows records to reference each other. For example, processor records usually reference cache memory records using their handles.
• A type. The SMBIOS specification defines different types of elements a computer can be made of. In this example, the type is 2, which means that the record contains "Base Board Information".
• A size. Each record has a 4-byte header (2 for the handle, 1 for the type, 1 for the size), the rest is used by the record data. This value doesn't take text strings into account (these are placed at the end of the record), so the actual length of the record may be (and is often) greater than the displayed value.
• Decoded values. The information presented of course depends on the type of record. Here, we learn about the board's manufacturer, model, version and serial number.
-d, --dev-mem FILE Read memory from device FILE (default: /dev/mem)
-q, --quiet Be less verbose. Unknown, inactive and OEM-specific entries are not displayed. Meta-data and handle references are hidden.
-s, --string KEYWORD Only display the value of the DMI string identified by KEYWORD. KEYWORD must be a keyword from the following list: bios-vendor, bios-version, bios-release-date, bios-revision, firmware-revision, system-manufacturer, system-product-name, system-version, system- serial-number, system-uuid, system-sku-number, system-family, baseboard-manufacturer, baseboard-product-name, baseboard-version, baseboard-serial-number, baseboard-asset-tag, chassis- manufacturer, chassis-type, chassis-version, chassis-serial- number, chassis-asset-tag, processor-family, processor- manufacturer, processor-version, processor-frequency.  Each keyword corresponds to a given DMI type and a given offset within this entry type.  Not all strings may be meaningful or even defined on all systems. Some keywords may return more than one result on some systems (e.g.  processor-version on a multi- processor system).  If KEYWORD is not provided or not valid, a list of all valid keywords is printed and dmidecode exits with an error.  This option cannot be used more than once.
Note: on Linux, most of these strings can alternatively be read directly from sysfs, typically from files under /sys/devices/virtual/dmi/id.  Most of these files are even readable by regular users.
-t, --type TYPE Only display the entries of type TYPE. TYPE can be either a DMI type number, or a comma-separated list of type numbers, or a keyword from the following list: bios, system, baseboard, chassis, processor, memory, cache, connector, slot. Refer to the DMI TYPES section below for details.  If this option is used more than once, the set of displayed entries will be the union of all the given types.  If TYPE is not provided or not valid, a list of all valid keywords is printed and dmidecode exits with an error.
-H, --handle HANDLE Only display the entry whose handle matches HANDLE.  HANDLE is a 16-bit integer.
-u, --dump Do not decode the entries, dump their contents as hexadecimal instead.  Note that this is still a text output, no binary data will be thrown upon you. The strings attached to each entry are displayed as both hexadecimal and ASCII. This option is mainly useful for debugging.
--dump-bin FILE Do not decode the entries, instead dump the DMI data to a file in binary form. The generated file is suitable to pass to --from-dump later.
--from-dump FILE Read the DMI data from a binary file previously generated using --dump-bin.
--no-sysfs Do not attempt to read DMI data from sysfs files. This is mainly useful for debugging.
--oem-string N Only display the value of the OEM string number N. The first OEM string has number 1. With special value "count", return the number of OEM strings instead.
-h, --help Display usage information and exit
-V, --version Display the version and exit
Options --string, --type, --dump-bin and --oem-string determine the output format and are mutually exclusive.
Please note in case of dmidecode is run on a system with BIOS that boasts new SMBIOS specification, which is not supported by the tool yet, it will print out relevant message in addition to requested data on the very top of the output. Thus informs the output data is not reliable.
The SMBIOS specification defines the following DMI types:
Type   Information ──────────────────────────────────────────── 0   BIOS 1   System 2   Baseboard 3   Chassis 4   Processor 5   Memory Controller 6   Memory Module 7   Cache 8   Port Connector 9   System Slots 10   On Board Devices 11   OEM Strings 12   System Configuration Options 13   BIOS Language 14   Group Associations 15   System Event Log 16   Physical Memory Array 17   Memory Device 18   32-bit Memory Error 19   Memory Array Mapped Address 20   Memory Device Mapped Address 21   Built-in Pointing Device 22   Portable Battery 23   System Reset 24   Hardware Security 25   System Power Controls 26   Voltage Probe 27   Cooling Device 28   Temperature Probe 29   Electrical Current Probe 30   Out-of-band Remote Access 31   Boot Integrity Services 32   System Boot 33   64-bit Memory Error 34   Management Device 35   Management Device Component 36   Management Device Threshold Data 37   Memory Channel 38   IPMI Device 39   Power Supply 40   Additional Information 41   Onboard Devices Extended Information 42   Management Controller Host Interface
Additionally, type 126 is used for disabled entries and type 127 is an end-of-table marker. Types 128 to 255 are for OEM-specific data. dmidecode will display these entries by default, but it can only decode them when the vendors have contributed documentation or code for them.
Keywords can be used instead of type numbers with --type.  Each keyword is equivalent to a list of type numbers:
Keyword     Types ────────────────────────────── bios        0, 13 system      1, 12, 15, 23, 32 baseboard   2, 10, 41 chassis     3 processor   4 memory      5, 6, 16, 17 cache       7 connector   8 slot        9
Keywords are matched case-insensitively. The following command lines are equivalent:
• dmidecode --type 0 --type 13
• dmidecode --type 0,13
• dmidecode --type bios
• dmidecode --type BIOS
The binary dump files generated by --dump-bin and read using --from-dump are formatted as follows:
• The SMBIOS or DMI entry point is located at offset 0x00.  It is crafted to hard-code the table address at offset 0x20.
• The DMI table is located at offset 0x20.
There is some ambiguity about how to interpret the UUID fields prior to SMBIOS specification version 2.6. There was no mention of byte swapping, and RFC 4122 says that no byte swapping should be applied by default. However, SMBIOS specification version 2.6 (and later) explicitly states that the first 3 fields of the UUID should be read as little-endian numbers (byte-swapped).  Furthermore, it implies that the same was already true for older versions of the specification, even though it was not mentioned. In practice, many hardware vendors were not byte-swapping the UUID. So, in order to preserve compatibility, it was decided to interpret the UUID fields according to RFC 4122 (no byte swapping) when the SMBIOS version is older than 2.6, and to interpret the first 3 fields as little-endian (byte-swapped) when the SMBIOS version is 2.6 or later. The Linux kernel follows the same logic.
/dev/mem /sys/firmware/dmi/tables/smbios_entry_point (Linux only) /sys/firmware/dmi/tables/DMI (Linux only)
More often than not, information contained in the DMI tables is inaccurate, incomplete or simply wrong.
Alan Cox, Jean Delvare
biosdecode(8), mem(4), ownership(8), vpddecode(8)
TMUXINATOR(1)                     User Commands                    TMUXINATOR(1)
tmuxinator - manage complex tmux sessions easily
tmuxinator [COMMANDS] [OPTION]
Lists commands available in tmuxinator
completions [arg1 arg2]
Used for shell completion
copy [EXISTING] [NEW]
Copy an existing project to a new project and open it in your editor
debug [PROJECT] [ARGS]
Output the shell commands that are generated by tmuxinator
delete [PROJECT1] [PROJECT2] ...
Deletes given project
Look for problems in your configuration
help [COMMAND]
Describe available commands or one specific command
Deletes all tmuxinator projects
Lists all tmuxinator projects
Start a tmux session using ./.tmuxinator.yml
new [PROJECT] [SESSION]
Create a new project file and open it in your editor
start [PROJECT] [ARGS]
Start a tmux session using a project's name (with an optional [ALIAS] for project reuse) or a path to a project config file (via the -p flag)
stop [PROJECT]
Stop a tmux session using a project's tmuxinator config
Display installed tmuxinator version
Copyright (c) 2010-2014 Allen Bargi, Christopher Chow.  See /usr/share/doc/tmuxinator/copyright for further details.
This manual page was written by Youhei SASAKI <uwabami@gfd-dennou.org>, for the Debian project (but may ber used others).
GIT-FORK(1)                        Git Extras                        GIT-FORK(1)
git-fork - Fork a repo on github
git-fork [<github-repo-url>]
If a github repo url is given, fork the repo. Like clone but forks first.
1.  forks the repo on github
2.  clones the repo into the current dir
3.  adds the original repo as a remote called upstream
If a url is not given and the current dir is a github repo, fork the repo.
1.  forks the current repo
2.  rename the origin remote repo to upstream
3.  adds the forked repo as a remote called origin
Remotes will use ssh if you have it configured with GitHub, if not, https will be used.
Fork expect.js:
$ git fork https://github.com/LearnBoost/expect.js
or just:
$ git fork LearnBoost/expect.js
$ ..<forks into your github profile and clones repo locally to expect.js dir>...
$ cd expect.js && git remote -v
origin          git@github.com:<user>/expect.js (fetch) origin          git@github.com:<user>/expect.js (push) upstream        git@github.com:LearnBoost/expect.js (fetch) upstream        git@github.com:LearnBoost/expect.js (push)
If the current dir is a clone of expect.js, this has the same effect:
$ git fork
Written by Andrew Griffiths <mail@andrewgriffithsonline.com>
GIT-INFO(1)                        Git Extras                        GIT-INFO(1)
git-info - Returns information on current repository
Shows the following information about a repository:
1.  Remote Url(s)
2.  Remote Branches
3.  Local Branches
4.  Most recent commit
5.  Configuration Info
Outputs info about a repo:
$ git info
## Remote URLs:
origin      git@github.com:sampleAuthor/git-extras.git (fetch) origin      git@github.com:sampleAuthor/git-extras.git (push)
## Remote Branches:
origin/HEAD -> origin/master origin/myBranch
## Local Branches:
myBranch * master
## Most Recent Commit:
commit e3952df2c172c6f3eb533d8d0b1a6c77250769a7 Author: Sample Author <sampleAuthor@gmail.com>
Added git-info command.
Type ´git log´ for more commits, or ´git show <commit id>´ for full commit details.
## Configuration (.git/config):
color.diff=auto color.status=auto color.branch=auto user.name=Sample Author user.email=sampleAuthor@gmail.com core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true core.ignorecase=true remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* remote.origin.url=git@github.com:mub/git-extras.git branch.master.remote=origin branch.master.merge=refs/heads/master
GROUPADD(1M)                                                        GROUPADD(1M)
groupadd - 新しいグループを作成する
groupadd [ -g gid [ -o ] ] group
groupaddコマンドはコマンドライン上で指定された値及び システムのディフォルト値を用いて新しいグループを作成する。 新しいグループは必要となった際にシステムファイルに記入される。 groupaddコマンドに指定できるオプションは次のものである
-g gid 新規グループのID番号。 この値は、-oオプションを用いない限りは、他と重複してはならない。 また、非負値でなくてはならない。 ディフォルトは、99より大きく且つ他の全ての既存グループのIDよりも 大きなものの中で最小のものである。 0から99迄の値は大抵システム用のアカウントに予約されている。
/etc/group - グループのアカウント情報 /etc/gshadow - グループの安全なアカウント情報
chfn(1), chsh(1), useradd(1M), userdel(1M), usermod(1M), passwd(1), groupdel(1M), groupmod(1M)
docker-login - Log in to a Docker registry
docker login [OPTIONS] [SERVER]
Log in to a Docker Registry located on the specified SERVER.  You can specify a URL or a hostname for the SERVER value. If you do not specify a SERVER, the command uses Docker's public registry located at https://registry-1.docker.io/ by default.  To get a username/password for Docker's public registry, create an account on Docker Hub.
docker login requires user to use sudo or be root, except when:
1. connecting to  a remote daemon, such as a docker-machine provisioned docker engine.
2. user is added to the docker group.  This will impact the security of your system; the docker group is root equivalent. See Docker Daemon Attack Surface ⟨https://docs.docker.com/engine/security/#docker-daemon- attack-surface⟩ for details.
You can log into any public or private repository for which you have credentials.  When you log in, the command stores encoded credentials in $HOME/.docker/config.json on Linux or %USERPROFILE%/.docker/config.json on Windows.
Login to a registry on your localhost # docker login localhost:8080
See also docker-logout(1) to log out from a Docker registry.
-h, --help[=false]      help for login
-p, --password=""      Password
--password-stdin[=false]      Take the password from stdin
-u, --username=""      Username
FATLABEL(8)                  System Manager's Manual                 FATLABEL(8)
fatlabel - set or get MS-DOS filesystem label or volume ID
fatlabel [OPTIONS] DEVICE [NEW]
fatlabel will display or change the volume label or volume ID on the MS- DOS filesystem located on DEVICE.  By default it works in label mode.  It can be switched to volume ID mode with the option -i or --volume-id.
If NEW is omitted, then the existing label or volume ID is written to the standard output.  A label can't be longer than 11 bytes and should be in all upper case for best compatibility.  An empty string or a label consisting only of white space is not allowed.  A volume ID must be given as a hexadecimal number (no leading "0x" or similar) and must fit into 32 bits.
-i, --volume-id Switch to volume ID mode.
-r, --reset Remove label in label mode or generate new ID in volume ID mode.
-c PAGE, --codepage=PAGE Use DOS codepage PAGE to encode/decode label.  By default codepage 850 is used.
-h, --help Display a help message and terminate.
-V, --version Show version number and terminate.
COMPATIBILITY and BUGS For historic reasons FAT label is stored in two different locations: in the boot sector and as a special volume label entry in the root directory.  MS-DOS 5.00, MS-DOS 6.22, MS-DOS 7.10, Windows 98, Windows XP and also Windows 10 read FAT label only from the root directory.  Absence of the volume label in the root directory is interpreted as empty or none label, even if boot sector contains some valid label.
When Windows XP or Windows 10 system changes a FAT label it stores it only in the root directory — letting boot sector unchanged.  Which leads to problems when a label is removed on Windows.  Old label is still stored in the boot sector but is removed from the root directory.
dosfslabel prior to the version 3.0.7 operated only with FAT labels stored in the boot sector, completely ignoring a volume label in the root directory.
dosfslabel in versions 3.0.7–3.0.15 reads FAT labels from the root directory and in case of absence, it fallbacks to a label stored in the boot sector.  Change operation resulted in updating a label in the boot sector and sometimes also in the root directory due to the bug.  That bug was fixed in dosfslabel version 3.0.16 and since this version dosfslabel updates label in both location.
Since version 4.2, fatlabel reads a FAT label only from the root directory (like MS-DOS and Windows systems), but changes a FAT label in both locations.  In version 4.2 was fixed handling of empty labels and labels which starts with a byte 0xE5.  Also in this version was added support for non-ASCII labels according to the specified DOS codepage and were added checks if a new label is valid.
It is strongly suggested to not use dosfslabel prior to version 3.0.16.
MS-DOS and Windows systems use DOS (OEM) codepage for encoding and decoding FAT label.  In Windows systems DOS codepage is global for all running applications and cannot be configured explicitly.  It is set implicitly by option Language for non-Unicode programs available in Regional and Language Options via Control Panel.  Default DOS codepage for fatlabel is 850.  See following mapping table between DOS codepage and Language for non-Unicode programs: