neulab/tldr huggingface dataset:
e2fsck is used to check the ext2/ext3/ext4 family of file systems.  For ext3 and ext4 file systems that use a journal, if the system has been shut down uncleanly without any errors, normally, after replaying the committed transactions  in the journal, the file system should be marked as clean.   Hence, for file systems that use journaling, e2fsck will normally replay the journal and exit, unless its superblock indicates that further checking is required.
device is a block device (e.g., /dev/sdc1) or file containing the file system.
Note that in general it is not safe to run e2fsck on mounted file systems.  The only exception is if the -n option is specified, and -c, -l, or -L options are not specified.   However, even if it is safe to do so, the results printed by e2fsck are not valid if the file system is mounted.   If e2fsck asks whether or not you should check a file system which is mounted, the only correct answer is ``no''.  Only experts who really know what they are doing should consider answering this question in any other way.
If e2fsck is run in interactive mode (meaning that none of -y, -n, or -p are specified), the program will ask the user to fix each problem found in the file system.  A response of 'y' will fix the error; 'n' will leave the error unfixed; and 'a' will fix the problem and all subsequent problems; pressing Enter will proceed with the default response, which is printed before the question mark.  Pressing Control-C terminates e2fsck immediately.
-a     This option does the same thing as the -p option.  It is provided for backwards compatibility only; it is suggested that people use -p option whenever possible.
-b superblock Instead of using the normal superblock, use an alternative superblock specified by superblock.  This option is normally used when the primary superblock has been corrupted.  The location of backup superblocks is dependent on the file system's blocksize, the number of blocks per group, and features such as sparse_super.
Additional backup superblocks can be determined by using the mke2fs program using the -n option to print out where the superblocks exist, supposing mke2fs is supplied with arguments that are consistent with the file system's layout (e.g. blocksize, blocks per group, sparse_super, etc.).
If an alternative superblock is specified and the file system is not opened read-only, e2fsck will make sure that the primary superblock is updated appropriately upon completion of the file system check.
-B blocksize Normally, e2fsck will search for the superblock at various different block sizes in an attempt to find the appropriate block size.  This search can be fooled in some cases.  This option forces e2fsck to only try locating the superblock at a particular blocksize.  If the superblock is not found, e2fsck will terminate with a fatal error.
-c     This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks.  If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory.  If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.
-C fd  This option causes e2fsck to write completion information to the specified file descriptor so that the progress of the file system check can be monitored.  This option is typically used by programs which are running e2fsck.  If the file descriptor number is negative, then absolute value of the file descriptor will be used, and the progress information will be suppressed initially.  It can later be enabled by sending the e2fsck process a SIGUSR1 signal. If the file descriptor specified is 0, e2fsck will print a completion bar as it goes about its business.  This requires that e2fsck is running on a video console or terminal.
-d     Print debugging output (useless unless you are debugging e2fsck).
-D     Optimize directories in file system.  This option causes e2fsck to try to optimize all directories, either by re-indexing them if the file system supports directory indexing,  or by sorting and compressing directories for smaller directories, or for file systems using traditional linear directories.
Even without the -D option, e2fsck may sometimes optimize a few directories --- for example, if directory indexing is enabled and a directory is not indexed and would benefit from being indexed, or if the index structures are corrupted and need to be rebuilt. The -D option forces all directories in the file system to be optimized.  This can sometimes make them a little smaller and slightly faster to search, but in practice, you should rarely need to use this option.
The -D option will detect directory entries with duplicate names in a single directory, which e2fsck normally does not enforce for performance reasons.
-E extended_options Set e2fsck extended options.  Extended options are comma separated, and may take an argument using the equals ('=') sign. The following options are supported:
ea_ver=extended_attribute_version Set the version of the extended attribute blocks which e2fsck will require while checking the file system. The version number may be 1 or 2.  The default extended attribute version format is 2.
journal_only Only replay the journal if required, but do not perform any further checks or repairs.
fragcheck During pass 1, print a detailed report of any discontiguous blocks for files in the file system.
discard Attempt to discard free blocks and unused inode blocks after the full file system check (discarding blocks is useful on solid state devices and sparse / thin- provisioned storage). Note that discard is done in pass 5 AFTER the file system has been fully checked and only if it does not contain recognizable errors. However there might be cases where e2fsck does not fully recognize a problem and hence in this case this option may prevent you from further manual data recovery.
nodiscard Do not attempt to discard free blocks and unused inode blocks. This option is exactly the opposite of discard option. This is set as default.
no_optimize_extents Do not offer to optimize the extent tree by eliminating unnecessary width or depth.  This can also be enabled in the options section of /etc/e2fsck.conf.
optimize_extents Offer to optimize the extent tree by eliminating unnecessary width or depth.  This is the default unless otherwise specified in /etc/e2fsck.conf.
inode_count_fullmap Trade off using memory for speed when checking a file system with a large number of hard-linked files.  The amount of memory required is proportional to the number of inodes in the file system.  For large file systems, this can be gigabytes of memory.  (For example, a 40TB file system with 2.8 billion inodes will consume an additional 5.7 GB memory if this optimization is enabled.)  This optimization can also be enabled in the options section of /etc/e2fsck.conf.
no_inode_count_fullmap Disable the inode_count_fullmap optimization.  This is the default unless otherwise specified in /etc/e2fsck.conf.
readahead_kb Use this many KiB of memory to pre-fetch metadata in the hopes of reducing e2fsck runtime.  By default, this is set to the size of two block groups' inode tables (typically 4MiB on a regular ext4 file system); if this amount is more than 1/50th of total physical memory, readahead is disabled.  Set this to zero to disable readahead entirely.
bmap2extent Convert block-mapped files to extent-mapped files.
fixes_only Only fix damaged metadata; do not optimize htree directories or compress extent trees.  This option is incompatible with the -D and -E bmap2extent options.
check_encoding Force verification of encoded filenames in case- insensitive directories.  This is the default mode if the file system has the strict flag enabled.
unshare_blocks If the file system has shared blocks, with the shared blocks read-only feature enabled, then this will unshare all shared blocks and unset the read-only feature bit. If there is not enough free space then the operation will fail.  If the file system does not have the read-only feature bit, but has shared blocks anyway, then this option will have no effect. Note when using this option, if there is no free space to clone blocks, there is no prompt to delete files and instead the operation will fail.
Note that unshare_blocks implies the "-f" option to ensure that all passes are run. Additionally, if "-n" is also specified, e2fsck will simulate trying to allocate enough space to deduplicate. If this fails, the exit code will be non-zero.
-f     Force checking even if the file system seems clean.
-F     Flush the file system device's buffer caches before beginning. Only really useful for doing e2fsck time trials.
-j external-journal Set the pathname where the external-journal for this file system can be found.
-k     When combined with the -c option, any existing bad blocks in the bad blocks list are preserved, and any new bad blocks found by running badblocks(8) will be added to the existing bad blocks list.
-l filename Add the block numbers listed in the file specified by filename to the list of bad blocks.  The format of this file is the same as the one generated by the badblocks(8) program.  Note that the block numbers are based on the blocksize of the file system. Hence, badblocks(8) must be given the blocksize of the file system in order to obtain correct results.  As a result, it is much simpler and safer to use the -c option to e2fsck, since it will assure that the correct parameters are passed to the badblocks program.
-L filename Set the bad blocks list to be the list of blocks specified by filename.  (This option is the same as the -l option, except the bad blocks list is cleared before the blocks listed in the file are added to the bad blocks list.)
-n     Open the file system read-only, and assume an answer of `no' to all questions.  Allows e2fsck to be used non-interactively.  This option may not be specified at the same time as the -p or -y options.
-p     Automatically repair ("preen") the file system.  This option will cause e2fsck to automatically fix any file system problems that can be safely fixed without human intervention.  If e2fsck discovers a problem which may require the system administrator to take additional corrective action, e2fsck will print a description of the problem and then exit with the value 4 logically or'ed into the exit code.  (See the EXIT CODE section.)  This option is normally used by the system's boot scripts.  It may not be specified at the same time as the -n or -y options.
-r     This option does nothing at all; it is provided only for backwards compatibility.
-t     Print timing statistics for e2fsck.  If this option is used twice, additional timing statistics are printed on a pass by pass basis.
-V     Print version information and exit.
-y     Assume an answer of `yes' to all questions; allows e2fsck to be used non-interactively.  This option may not be specified at the same time as the -n or -p options.
-z undo_file Before overwriting a file system block, write the old contents of the block to an undo file.  This undo file can be used with e2undo(8) to restore the old contents of the file system should something go wrong.  If the empty string is passed as the undo_file argument, the undo file will be written to a file named e2fsck-device.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR environment variable.
The exit code returned by e2fsck is the sum of the following conditions: 0    - No errors 1    - File system errors corrected 2    - File system errors corrected, system should be rebooted 4    - File system errors left uncorrected 8    - Operational error 16   - Usage or syntax error 32   - E2fsck canceled by user request 128  - Shared library error
The following signals have the following effect when sent to e2fsck.
SIGUSR1 This signal causes e2fsck to start displaying a completion bar or emitting progress information.  (See discussion of the -C option.)
SIGUSR2 This signal causes e2fsck to stop displaying a completion bar or emitting progress information.
Almost any piece of software will have bugs.  If you manage to find a file system which causes e2fsck to crash, or which e2fsck is unable to repair, please report it to the author.
Please include as much information as possible in your bug report. Ideally, include a complete transcript of the e2fsck run, so I can see exactly what error messages are displayed.  (Make sure the messages printed by e2fsck are in English; if your system has been configured so that e2fsck's messages have been translated into another language, please set the the LC_ALL environment variable to C so that the transcript of e2fsck's output will be useful to me.)  If you have a writable file system where the transcript can be stored, the script(1) program is a handy way to save the output of e2fsck to a file.
It is also useful to send the output of dumpe2fs(8).  If a specific inode or inodes seems to be giving e2fsck trouble, try running the debugfs(8) command and send the output of the stat(1u) command run on the relevant inode(s).  If the inode is a directory, the debugfs dump command will allow you to extract the contents of the directory inode, which can sent to me after being first run through uuencode(1).  The most useful data you can send to help reproduce the bug is a compressed raw image dump of the file system, generated using e2image(8).  See the e2image(8) man page for more details.
Always include the full version string which e2fsck displays when it is run, so I know which version you are running.
E2FSCK_CONFIG Determines the location of the configuration file (see e2fsck.conf(5)).
This version of e2fsck was written by Theodore Ts'o <tytso@mit.edu>.
e2fsck.conf(5), badblocks(8), dumpe2fs(8), debugfs(8), e2image(8), mke2fs(8), tune2fs(8)
PWDX(1)                           User Commands                          PWDX(1)
pwdx - report current working directory of a process
pwdx [options] pid [...]
-h, --help Output help screen and exit.
ps(1), pgrep(1)
No standards apply, but pwdx looks an awful lot like a SunOS command.
Nicholas Miell ⟨nmiell@gmail.com⟩ wrote pwdx in 2004.
JOIN(1P)                    POSIX Programmer's Manual                   JOIN(1P)
join — relational database operator
join [-a file_number|-v file_number] [-e string] [-o list] [-t char] [-1 field] [-2 field] file1 file2
The join utility shall perform an equality join on the files file1 and file2.  The joined files shall be written to the standard output.
The join field is a field in each file on which the files are compared. The join utility shall write one line in the output for each pair of lines in file1 and file2 that have join fields that collate equally. The output line by default shall consist of the join field, then the remaining fields from file1, then the remaining fields from file2.  This format can be changed by using the -o option (see below). The -a option can be used to add unmatched lines to the output. The -v option can be used to output only unmatched lines.
The files file1 and file2 shall be ordered in the collating sequence of sort -b on the fields on which they shall be joined, by default the first in each line. All selected output shall be written in the same collating sequence.
The default input field separators shall be <blank> characters. In this case, multiple separators shall count as one field separator, and leading separators shall be ignored. The default output field separator shall be a <space>.
The field separator and collating sequence can be changed by using the -t option (see below).
If the same key appears more than once in either file, all combinations of the set of remaining fields in file1 and the set of remaining fields in file2 are output in the order of the lines encountered.
If the input files are not in the appropriate collating sequence, the results are unspecified.
The join utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-a file_number Produce a line for each unpairable line in file file_number, where file_number is 1 or 2, in addition to the default output. If both -a1 and -a2 are specified, all unpairable lines shall be output.
-e string Replace empty output fields in the list selected by -o with the string string.
-o list   Construct the output line to comprise the fields specified in list, each element of which shall have one of the following two forms:
1. file_number.field, where file_number is a file number and field is a decimal integer field number
2. 0 (zero), representing the join field
The elements of list shall be either <comma>-separated or <blank>-separated, as specified in Guideline 8 of the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.  The fields specified by list shall be written for all selected output lines. Fields selected by list that do not appear in the input shall be treated as empty output fields. (See the -e option.) Only specifically requested fields shall be written. The application shall ensure that list is a single command line argument.
-t char   Use character char as a separator, for both input and output. Every appearance of char in a line shall be significant. When this option is specified, the collating sequence shall be the same as sort without the -b option.
-v file_number Instead of the default output, produce a line only for each unpairable line in file_number, where file_number is 1 or 2. If both -v1 and -v2 are specified, all unpairable lines shall be output.
-1 field  Join on the fieldth field of file 1. Fields are decimal integers starting with 1.
-2 field  Join on the fieldth field of file 2. Fields are decimal integers starting with 1.
file1, file2 A pathname of a file to be joined. If either of the file1 or file2 operands is '-', the standard input shall be used in its place.
The standard input shall be used only if the file1 or file2 operand is '-'.  See the INPUT FILES section.
The following environment variables shall affect the execution of join:
LC_COLLATE Determine the locale of the collating sequence join expects to have been used when the input files were sorted.
The join utility output shall be a concatenation of selected character fields.  When the -o option is not specified, the output shall be:
"%s%s%s\n", <join field>, <other file1 fields>, <other file2 fields>
If the join field is not the first field in a file, the <other file fields> for that file shall be:
<fields preceding join field>, <fields following join field>
When the -o option is specified, the output format shall be:
"%s\n", <concatenation of fields>
where the concatenation of fields is described by the -o option, above.
For either format, each field (except the last) shall be written with its trailing separator character. If the separator is the default (<blank> characters), a single <space> shall be written after each field (except the last).
Pathnames consisting of numeric digits or of the form string.string should not be specified directly following the -o list.
If the collating sequence of the current locale does not have a total ordering of all characters (see the Base Definitions volume of POSIX.1‐2017, Section 7.3.2, LC_COLLATE), join treats fields that collate equally but are not identical as being the same. If this behavior is not desired, it can be avoided by forcing the use of the POSIX locale (although this means re-sorting the input files into the POSIX locale collating sequence.)
When using join to process pathnames, it is recommended that LC_ALL, or at least LC_CTYPE and LC_COLLATE, are set to POSIX or C in the environment, since pathnames can contain byte sequences that do not form valid characters in some locales, in which case the utility's behavior would be undefined. In the POSIX locale each byte is a valid single-byte character, and therefore this problem is avoided.
The -o 0 field essentially selects the union of the join fields. For example, given file phone:
!Name           Phone Number Don             +1 123-456-7890 Hal             +1 234-567-8901 Yasushi         +2 345-678-9012
and file fax:
!Name           Fax Number Don             +1 123-456-7899 Keith           +1 456-789-0122 Yasushi         +2 345-678-9011
(where the large expanses of white space are meant to each represent a single <tab>), the command:
join -t "<tab>" -a 1 -a 2 -e '(unknown)' -o 0,1.2,2.2 phone fax
(where <tab> is a literal <tab> character) would produce:
!Name           Phone Number            Fax Number Don             +1 123-456-7890         +1 123-456-7899 Hal             +1 234-567-8901         (unknown) Keith           (unknown)               +1 456-789-0122 Yasushi         +2 345-678-9012         +2 345-678-9011
Multiple instances of the same key will produce combinatorial results. The following:
fa: a x a y a z fb: a p
will produce:
a x p a y p a z p
And the following:
fa: a b c a d e fb: a w x a y z a o p
a b c w x a b c y z a b c o p a d e w x a d e y z a d e o p
The -e option is only effective when used with -o because, unless specific fields are identified using -o, join is not aware of what fields might be empty. The exception to this is the join field, but identifying an empty join field with the -e string is not historical practice and some scripts might break if this were changed.
The 0 field in the -o list was adopted from the Tenth Edition version of join to satisfy international objections that the join in the base documents for IEEE Std 1003.2‐1992 did not support the ``full join'' or ``outer join'' described in relational database literature.  Although it has been possible to include a join field in the output (by default, or by field number using -o), the join field could not be included for an unpaired line selected by -a.  The -o 0 field essentially selects the union of the join fields.
This sort of outer join was not possible with the join commands in the base documents for IEEE Std 1003.2‐1992. The -o 0 field was chosen because it is an upwards-compatible change for applications. An alternative was considered: have the join field represent the union of the fields in the files (where they are identical for matched lines, and one or both are null for unmatched lines). This was not adopted because it would break some historical applications.
The ability to specify file2 as - is not historical practice; it was added for completeness.
The -v option is not historical practice, but was considered necessary because it permitted the writing of only those lines that do not match on the join field, as opposed to the -a option, which prints both lines that do and do not match. This additional facility is parallel with the -v option of grep.
Some historical implementations have been encountered where a blank line in one of the input files was considered to be the end of the file; the description in this volume of POSIX.1‐2017 does not cite this as an allowable case.
Earlier versions of this standard allowed -j, -j1, -j2 options, and a form of the -o option that allowed the list option-argument to be multiple arguments. These forms are no longer specified by POSIX.1‐2008 but may be present in some implementations.
awk, comm, sort, uniq
FG(1P)                      POSIX Programmer's Manual                     FG(1P)
fg — run jobs in the foreground
fg [job_id]
If job control is enabled (see the description of set -m), the fg utility shall move a background job from the current environment (see Section 2.12, Shell Execution Environment) into the foreground.
Using fg to place a job into the foreground shall remove its process ID from the list of those ``known in the current shell execution environment''; see Section 2.9.3.1, Examples.
job_id    Specify the job to be run as a foreground job. If no job_id operand is given, the job_id for the job that was most recently suspended, placed in the background, or run as a background job shall be used. The format of job_id is described in the Base Definitions volume of POSIX.1‐2017, Section 3.204, Job Control Job ID.
The following environment variables shall affect the execution of fg:
The fg utility shall write the command line of the job to standard output in the following format:
"%s\n", <command>
If job control is disabled, the fg utility shall exit with an error and no job shall be placed in the foreground.
The fg utility does not work as expected when it is operating in its own utility execution environment because that environment has no applicable jobs to manipulate. See the APPLICATION USAGE section for bg.  For this reason, fg is generally implemented as a shell regular built-in.
Section 2.9.3.1, Examples, Section 2.12, Shell Execution Environment, bg, kill, jobs, wait
The Base Definitions volume of POSIX.1‐2017, Section 3.204, Job Control Job ID, Chapter 8, Environment Variables
DIRNAME(1)                        User Commands                       DIRNAME(1)
dirname - strip last component from file name
dirname [OPTION] NAME...
Output each NAME with its last non-slash component and trailing slashes removed; if NAME contains no /'s, output '.' (meaning the current directory).
dirname /usr/bin/ -> "/usr"
dirname dir1/str dir2/str -> "dir1" followed by "dir2"
dirname stdio.h -> "."
basename(1), readlink(1)
Full documentation <https://www.gnu.org/software/coreutils/dirname> or available locally via: info '(coreutils) dirname invocation'
MD5SUM(1)                         User Commands                        MD5SUM(1)
md5sum - compute and check MD5 message digest
md5sum [OPTION]... [FILE]...
Print or check MD5 (128-bit) checksums.
The sums are computed as described in RFC 1321.  When checking, the input should be a former output of this program.  The default mode is to print a line with: checksum, a space, a character indicating input mode ('*' for binary, ' ' for text or where binary is insignificant), and name for each FILE.
Do not use the MD5 algorithm for security related purposes.  Instead, use an SHA-2 algorithm, implemented in the programs sha224sum(1), sha256sum(1), sha384sum(1), sha512sum(1), or the BLAKE2 algorithm, implemented in b2sum(1)
Full documentation <https://www.gnu.org/software/coreutils/md5sum> or available locally via: info '(coreutils) md5sum invocation'
MITMPROXY(1)                                                        MITMPROXY(1)
mitmproxy - a man-in-the-middle proxy with a console interface
mitmproxy [options]
mitmproxy is a console tool that allows interactive examination and modification of HTTP traffic.  It differs from mitmdump in that all flows are kept in memory, which means that it's intended for taking and manipulating smallish samples.  Use the ? shortcut key to view, context-sensitive documentation from any mitmproxy screen.
--palette {dark|light|lowdark|lowlight|solarized_dark|solarized_light} Select color palette: dark, light, lowdark, lowlight, solarized_dark or solarized_light.
--palette-transparent Set transparent background for palette.
-e, --eventlog Show event log.
--follow Follow flow list.
--no-mouse Disable mouse interaction.
Filters: See help in mitmproxy for filter expression syntax.
-i INTERCEPT, --intercept INTERCEPT Intercept filter expression.
-f FILTER, --filter FILTER Filter view expression.
~/.mitmproxy/mitmproxy.conf Settings for mitmproxy.  This file can contain any options supported by mitmproxy.
Options that start with -- (e.g.  --version) can also be set in a config file (~/.mitmproxy/common.conf or ~/.mitmproxy/mitmproxy.conf or specified via --conf).  Config file syntax allows:
mitmproxy was written by Aldo Cortesi.
This manual page was written by Alex Chernyakhovsky <achernya@mit.edu> for the Debian GNU/Linux system, but its use elsewhere is encouraged.
mitmproxy documentation and examples are available online at <http://docs.mitmproxy.org/en/latest/mitmproxy.html>.
PRINTENV(1)                       User Commands                      PRINTENV(1)
printenv - print all or part of environment
printenv [OPTION]... [VARIABLE]...
Print the values of the specified environment VARIABLE(s).  If no VARIABLE is specified, print name and value pairs for them all.
NOTE: your shell may have its own version of printenv, which usually supersedes the version described here.  Please refer to your shell's documentation for details about the options it supports.
Written by David MacKenzie and Richard Mlynarik.
Full documentation <https://www.gnu.org/software/coreutils/printenv> or available locally via: info '(coreutils) printenv invocation'
FLAKE8(1)                    General Commands Manual                   FLAKE8(1)
flake8 - code checker using pycodestyle and pyflakes
flake8 [options] input ...
flake8 is a command-line utility for enforcing style consistency across Python projects. By default it includes lint checks provided by the PyFlakes project, PEP-0008 inspired style checks provided by the PyCodeStyle project, and McCabe complexity checking provided by the McCabe project. It will also run third-party extensions if they are found and installed.
-v, --verbose print more information about what is happening in flake8. This option is repeatable and will increase verbosity each time it is repeated.
-q, --quiet report only file names, or nothing. This option is repeatable.
--count print total number of errors and warnings to standard error and set the exit code to 1 if total is not empty.
--diff report changes only within line number ranges in the unified diff provided on standard in by the user.
--exclude=patterns comma-separated list of files or directories to exclude. (Default: .svn,CVS,.bzr,.hg,.git,__pycache__,.tox,.eggs,*.egg)
--filename=patterns only check for filenames matching the patterns in this comma-separated list. (Default: *.py)
--stdin-display-name=STDIN_DISPLAY_NAME the name used when reporting errors from code passed via stdin. This is useful for editors piping the file contents to flake8. (Default: stdin)
--format=format format errors according to the chosen formatter.
--hang-closing hang closing bracket instead of matching indentation of opening bracket's line.
--ignore=errors comma-separated list of errors and warnings to ignore (or skip). For example, --ignore=E4,E51,W234.  (Default: E121,E123,E126,E226,E24,E704,W503,W504)
--max-line-length=n maximum allowed line length for the entirety of this run. (Default: 79)
--select=errors comma-separated list of errors and warnings to enable.  For example, --select=E4,E51,W234. (Default: E,F,W,C90)
--disable-noqa disable the effect of "# noqa". This will report errors on lines with "# noqa" at the end.
--show-source show the source generate each error or warning.
--statistics count errors and warnings.
--enable-extensions=ENABLE_EXTENSIONS enable plugins and extensions that are otherwise disabled by default
--exit-zero exit with status code "0" even if there are errors.
--install-hook=INSTALL_HOOK install a hook that is run prior to a commit for the supported version control system.
-j JOBS, --jobs=JOBS number of subprocesses to use to run checks in parallel. This is ignored on Windows. The default, "auto", will auto-detect the number of processors available to use. (Default: auto)
--output-file=OUTPUT_FILE redirect report to a file.
--tee  write to stdout and output-file.
--append-config=APPEND_CONFIG provide extra config files to parse in addition to the files found by Flake8 by default. These files are the last ones read and so they take the highest precedence when multiple files provide the same option.
--config=CONFIG path to the config file that will be the authoritative config source. This will cause Flake8 to ignore all other configuration files.
--isolated ignore all found configuration files.
--benchmark print benchmark information about this run of Flake8
--max-complexity=MAX_COMPLEXITY McCabe complexity threshold
--bug-report print information necessary when preparing a bug report
--builtins=BUILTINS define more built-ins, comma separated
--doctests check syntax of the doctests
--include-in-doctest=INCLUDE_IN_DOCTEST run doctests only on these files
--exclude-from-doctest=EXCLUDE_FROM_DOCTEST skip these files when running doctests
The project options are read from the [flake8] section of the tox.ini file or the setup.cfg file located in any parent folder of the path(s) being processed.  Allowed options are: exclude, filename, select, ignore, max-line-length, hang-closing, count, format, quiet, showpep8, show-source, statistics, verbose, max-complexity, builtins.
GIT-CHECKOUT-INDEX(1)              Git Manual              GIT-CHECKOUT-INDEX(1)
git-checkout-index - Copy files from the index to the working tree
git checkout-index [-u] [-q] [-a] [-f] [-n] [--prefix=<string>] [--stage=<number>|all] [--temp] [-z] [--stdin] [--] [<file>...]
Will copy all files listed from the index to the working directory (not overwriting existing files).
-u, --index update stat information for the checked out entries in the index file.
-q, --quiet be quiet if files exist or are not in the index
-f, --force forces overwrite of existing files
-a, --all checks out all files in the index. Cannot be used together with explicit filenames.
-n, --no-create Donâ€™t checkout new files, only refresh files already checked out.
--prefix=<string> When creating files, prepend <string> (usually a directory including a trailing /)
--stage=<number>|all Instead of checking out unmerged entries, copy out the files from named stage. <number> must be between 1 and 3. Note: --stage=all automatically implies --temp.
--temp Instead of copying the files to the working directory write the content to temporary files. The temporary name associations will be written to stdout.
-z Only meaningful with --stdin; paths are separated with NUL character instead of LF.
The order of the flags used to matter, but not anymore.
Just doing git checkout-index does nothing. You probably meant git checkout-index -a. And if you want to force it, you want git checkout-index -f -a.
Intuitiveness is not the goal here. Repeatability is. The reason for the "no arguments means no work" behavior is that from scripts you are supposed to be able to do:
$ find . -name '*.h' -print0 | xargs -0 git checkout-index -f --
which will force all existing *.h files to be replaced with their cached copies. If an empty command line implied "all", then this would force-refresh everything in the index, which was not the point. But since git checkout-index accepts --stdin it would be faster to use:
$ find . -name '*.h' -print0 | git checkout-index -f -z --stdin
The -- is just a good idea when you know the rest will be filenames; it will prevent problems with a filename of, for example, -a. Using -- is probably a good policy in scripts.
USING --TEMP OR --STAGE=ALL When --temp is used (or implied by --stage=all) git checkout-index will create a temporary file for each index entry being checked out. The index will not be updated with stat information. These options can be useful if the caller needs all stages of all unmerged entries so that the unmerged files can be processed by an external merge tool.
A listing will be written to stdout providing the association of temporary file names to tracked path names. The listing format has two variations:
1. tempname TAB path RS
The first format is what gets used when --stage is omitted or is not --stage=all. The field tempname is the temporary file name holding the file content and path is the tracked path name in the index. Only the requested entries are output.
2. stage1temp SP stage2temp SP stage3tmp TAB path RS
The second format is what gets used when --stage=all. The three stage temporary fields (stage1temp, stage2temp, stage3temp) list the name of the temporary file if there is a stage entry in the index or .  if there is no stage entry. Paths which only have a stage 0 entry will always be omitted from the output.
In both formats RS (the record separator) is newline by default but will be the null byte if -z was passed on the command line. The temporary file names are always safe strings; they will never contain directory separators or whitespace characters. The path field is always relative to the current directory and the temporary file names are always relative to the top level directory.
If the object being copied out to a temporary file is a symbolic link the content of the link will be written to a normal file. It is up to the end-user or the Porcelain to make use of this information.
To update and refresh only the files already checked out
Using git checkout-index to "export an entire tree" The prefix ability basically makes it trivial to use git checkout-index as an "export as tree" function. Just read the desired tree into the index, and do:
$ git checkout-index --prefix=git-export-dir/ -a
git checkout-index will "export" the index into the specified directory.
The final "/" is important. The exported name is literally just prefixed with the specified string. Contrast this with the following example.
Export files with a prefix
$ git checkout-index --prefix=.merged- Makefile
This will check out the currently cached copy of Makefile into the file .merged-Makefile.
LYNX(1)                      General Commands Manual                     LYNX(1)
lynx - a general purpose distributed information browser for the World Wide Web
lynx [options] [optional paths or URLs]
lynx [options] [path or URL] -get_data data --
lynx [options] [path or URL] -post_data data --
Use “lynx -help” to display a complete list of current options.
Lynx is a fully-featured World Wide Web (WWW) client for users running cursor-addressable, character-cell display devices (e.g., vt100 terminals, vt100 emulators running on Windows 95/NT/XP/7/8 or any POSIX platform, or any other “curses-oriented” display).  It will display hypertext markup language (HTML) documents containing links to files residing on the local system, as well as files residing on remote systems running Gopher, HTTP, FTP, WAIS, and NNTP servers.  Current versions of Lynx run on Unix, VMS, Windows 95/NT/XP/7/8, DOS DJGPP and OS/2.
Lynx can be used to access information on the World Wide Web, or to build information systems intended primarily for local access.  For example, Lynx has been used to build several Campus Wide Information Systems (CWIS).  In addition, Lynx can be used to build systems isolated within a single LAN.
At start up, Lynx will load any local file or remote URL specified at the command line.  For help with URLs, press “?”  or “H” while running Lynx. Then follow the link titled, “Help on URLs.”
If more than one local file or remote URL is listed on the command line, Lynx will open only the last interactively.  All of the names (local files and remote URLs) are added to the G)oto history.
Lynx uses only long option names.  Option names can begin with double dash “--” as well, underscores and dashes can be intermixed in option names (in the reference below, options are shown with one dash “-” before them, and with underscores “_”).
Lynx provides many command-line options.  Some options require a value (string, number or keyword).  These are noted in the reference below. The other options set boolean values in the program.  There are three types of boolean options: set, unset and toggle.  If no option value is given, these have the obvious meaning: set (to true), unset (to false), or toggle (between true/false).  For any of these, an explicit value can be given in different forms to allow for operating system constraints, e.g.,
-center:off -center=off -center-
Lynx recognizes “1”, “+”, “on” and “true” for true values, and “0”, “-”, “off” and “false” for false values.  Other option-values are ignored.
The default boolean, number and string option values that are compiled into Lynx are displayed in the help-message provided by lynx -help.  Some of those may differ according to how Lynx was built; see the help message itself for these values.  The -help option is processed in the third pass of options-processing, so any option which sets a value, as well as runtime configuration values are reflected in the help-message.
-      If the argument is only “-”, then Lynx expects to receive the arguments from the standard input.  This is to allow for the potentially very long command line that can be associated with the -get_data or -post_data arguments (see below).  It can also be used to avoid having sensitive information in the invoking command line (which would be visible to other processes on most systems), especially when the -auth or -pauth options are used.
-accept_all_cookies accept all cookies.
-anonymous apply restrictions for anonymous account, see also -restrictions.
-assume_charset=MIMEname charset for documents that do not specify it.
-assume_local_charset=MIMEname charset assumed for local files, i.e., files which Lynx creates such as internal pages for the options menu.
-assume_unrec_charset=MIMEname use this instead of unrecognized charsets.
-auth=ID:PASSWD set authorization ID and password for protected documents at startup.  Be sure to protect any script files which use this switch.
-base  prepend a request URL comment and BASE tag to text/html outputs for -source dumps.
-bibhost=URL specify a local bibp server (default http://bibhost/).
-blink forces high intensity background colors for color mode, if available and supported by the terminal.  This applies to the slang library (for a few terminal emulators), or to OS/2 EMX with ncurses.
-book  use the bookmark page as the startfile.  The default or command line startfile is still set for the Main screen command, and will be used if the bookmark page is unavailable or blank.
-buried_news toggles scanning of news articles for buried references, and converts them to news links.  Not recommended because email addresses enclosed in angle brackets will be converted to false news links, and uuencoded messages can be trashed.
-cache=NUMBER set the NUMBER of documents cached in memory.  The default is 10.
-case  enable case-sensitive string searching.
-center Toggle center alignment in HTML TABLE.
-cfg=FILENAME specifies a Lynx configuration file other than the default lynx.cfg.
-child exit on left-arrow in startfile, and disable save to disk and associated print/mail options.
-child_relaxed exit on left-arrow in startfile, but allow save to disk and associated print/mail options.
-cmd_log=FILENAME write keystroke commands and related information to the specified file.
-cmd_script=FILENAME read keystroke commands from the specified file.  You can use the data written using the -cmd_log option.  Lynx will ignore other information which the command-logging may have written to the logfile.  Each line of the command script contains either a comment beginning with “#”, or a keyword:
exit causes the script to stop, and forces Lynx to exit immediately.
key the character value, in printable form.  Cursor and other special keys are given as names, e.g., “Down Arrow”.  Printable 7-bit ASCII codes are given as-is, and hexadecimal values represent other 8-bit codes.
set followed by a “name=value” allows one to override values set in the lynx.cfg or .lynxrc files.  Lynx tries the cfg-file setting first.
-collapse_br_tags toggles collapsing of BR tags.
-color forces color mode on, if available.  Default color control sequences which work for many terminal types are assumed if the terminal capability description does not specify how to handle color.  Lynx needs to be compiled with the slang library for this flag, it is equivalent to setting the COLORTERM environment variable.  (If color support is instead provided by a color- capable curses library like ncurses, Lynx relies completely on the terminal description to determine whether color mode is possible, and this flag is not needed and thus unavailable.)  A saved show_color=always setting found in a .lynxrc file at startup has the same effect.  A saved show_color=never found in .lynxrc on startup is overridden by this flag.
-connect_timeout=N Sets the connection timeout, where N is given in seconds.
-cookie_file=FILENAME specifies a file to use to read cookies.  If none is specified, the default value is ~/.lynx_cookies for most systems, but ~/cookies for MS-DOS.
-cookie_save_file=FILENAME specifies a file to use to store cookies.  If none is specified, the value given by -cookie_file is used.
-cookies toggles handling of Set-Cookie headers.
-core  toggles forced core dumps on fatal errors.  Turn this option off to ask Lynx to force a core dump if a fatal error occurs.
-crawl with -traversal, output each page to a file.  with -dump, format output as with -traversal, but to the standard output.
-curses_pads toggles the use of curses “pad” feature which supports left/right scrolling of the display.  The feature is normally available for curses configurations, but inactive.  To activate it, use the “|” character or the LINEWRAP_TOGGLE command.  Toggling this option makes the feature altogether unavailable.
-debug_partial separate incremental display stages with MessageSecs delay
-default_colors toggles the default-colors feature which is normally set in the lynx.cfg file.
-delay add DebugSecs delay after each progress-message
-display=DISPLAY set the display variable for X rexec-ed programs.
-display_charset=MIMEname set the charset for the terminal output.
-dont_wrap_pre inhibit wrapping of text when -dump'ing and -crawl'ing, mark wrapped lines of <pre> in interactive session.
-dump  dumps the formatted output of the default document or those specified on the command line to standard output.  Unlike interactive mode, all documents are processed.  This can be used in the following way:
lynx -dump http://www.subir.com/lynx.html
Files specified on the command line are formatted as HTML if their names end with one of the standard web suffixes such as “.htm” or “.html”.  Use the -force_html option to format files whose names do not follow this convention.
-editor=EDITOR enable external editing, using the specified EDITOR.  (vi, ed, emacs, etc.)
-emacskeys enable emacs-like key movement.
-enable_scrollback toggles compatibility with communication programs' scrollback keys (may be incompatible with some curses packages).
-error_file=FILE define a file where Lynx will report HTTP access codes.
-exec  enable local program execution (normally not configured).
-fileversions include all versions of files in local VMS directory listings.
-find_leaks toggle memory leak-checking.  Normally this is not compiled-into your executable, but when it is, it can be disabled for a session.
-force_empty_hrefless_a force HREF-less “A” elements to be empty (close them as soon as they are seen).
-force_html forces the first document to be interpreted as HTML.
This is most useful when processing files specified on the command line which have an unrecognized suffix (or the suffix is associated with a non-HTML type, such as “.txt” for plain text files).
Lynx recognizes these file suffixes as HTML:
“.ht3”, “.htm”, “.html3”, “.html”, “.htmlx”, “.php3”, “.php”, “.phtml”, “.sht”, and “.shtml”.
-force_secure toggles forcing of the secure flag for SSL cookies.
-forms_options toggles whether the Options Menu is key-based or form-based.
-from  toggles transmissions of From headers.
-ftp   disable ftp access.
-get_data properly formatted data for a get form are read in from the standard input and passed to the form.  Input is terminated by a line that starts with “---”.
Lynx issues an HTTP GET, sending the form to the path or URL given on the command-line and prints the response of the server.  If no path or URL is given, Lynx sends the form to the start-page.
-head  send a HEAD request for the mime headers.
-help  print the Lynx command syntax usage message, and exit.
-hiddenlinks=[option] control the display of hidden links.
merge hidden links show up as bracketed numbers and are numbered together with other links in the sequence of their occurrence in the document.
listonly hidden links are shown only on L)ist screens and listings generated by -dump or from the P)rint menu, but appear separately at the end of those lists.  This is the default behavior.
ignore hidden links do not appear even in listings.
-historical toggles use of “>” or “-->” as a terminator for comments.
-homepage=URL set homepage separate from start page.
-image_links toggles inclusion of links for all images.
-index=URL set the default index file to the specified URL.
-ismap toggles inclusion of ISMAP links when client-side MAPs are present.
-justify do justification of text.
-link=NUMBER starting count for lnk#.dat files produced by -crawl.
-list_inline for -dump, show the links inline with the text.
-listonly for -dump, show only the list of links.
-localhost disable URLs that point to remote hosts.
-locexec enable local program execution from local files only (if Lynx was compiled with local execution enabled).