neulab/tldr huggingface dataset:
feh -rSwidth -A "mv %F ~/images/%N" ~/Pictures View all images in ~/Pictures and below, sorted by width, move an image to ~/image/image_name when enter is pressed
feh --start-at ~/Pictures/foo.jpg View all images in ~/Pictures, starting with foo.jpg.  All other images are still in the slideshow and can be viewed normally
feh --start-at ~/Pictures/foo.jpg ~/Pictures Same as above.
feh --info "exifgrep '(Model|DateTimeOriginal|FNumber|ISO|Flash)' %F | cut -d . -f 4-" . Show some EXIF information, extracted by exifprobe/exifgrep
feh --action 'rm %F' -rl --max-dimension 1000x800 Recursively remove all images with dimensions below or equal to 1000x800 pixels from the current directory.
feh -L '%w %h %f' | awk '{ if ($1 > $2) { print $0 } }' | cut -d ' ' -f 3- | feh -f - Show landscape pictures (image width greater than height) in the current directory.
When --edit is used, feh needs the jpegtran and jpegexiforient binaries (usually distributed in "libjpeg-progs" or similar) for lossless JPEG rotation.
To view images from URLs such as "http://", feh must be compiled with libcurl support.  It is enabled in this build
Imlib2 releases prior to 1.7.4 are unable to load gif, tiff, and webp images if the filename does not end with gif, tiff, or webp, respectively. Notably, this means that feh is unable to show gif, tiff, and webp images from stdin or network URLs on systems using an Imlib2 version older than 1.7.4.
On systems with giflib 5.1.2, feh may be unable to load gif images.  For affected mips, mipsel and arm devices, gif support is completely broken, while on x86 / x86_64 gifs can usually only be loaded if they are the first image in the filelist.  This appears to be a bug in giflib, see ⟨https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813729⟩ for details. Workaround: Use --conversion-timeout 5 (or some other positive value) to load gifs with imagemagick instead, or downgrade to giflib 5.1.1, or upgrade to giflib 5.1.4.
While loading images using libcurl, feh will not react to key or mouse actions.
Thumbnail mode is somewhat inefficient, and because of that not nearly as fast as it could be.
--scale-down does not take window decorations into account and may therefore make the window slightly too large.
REPORTING BUGS If you find a bug, please report it to ⟨derf+feh@finalrewind.org⟩ or via ⟨https://github.com/derf/feh/issues⟩.  You are also welcome to direct any feh-related comments/questions/... to #feh on irc.oftc.net.
Please include the feh version ⟨the output of "feh --version"⟩, steps to reproduce the bug and, if necessary, images to reproduce it.
Copyright (C) 1999, 2000 by Paul Duncan.  Copyright (C) 1999, 2000 by Tom Gilbert and contributors.  Copyright (C) 2010-2020 by Daniel Friesel and contributors.
The above copyright notice and this permission notice shall be included in all copies of the Software and its documentation and acknowledgment shall be given in the documentation and software packages that this Software was used.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Current developer: Daniel Friesel ⟨derf@finalrewind.org⟩
Original author (no longer developing): Tom Gilbert ⟨feh_sucks@linuxbrit.co.uk⟩
Website: https://feh.finalrewind.org
IPCS(1P)                    POSIX Programmer's Manual                   IPCS(1P)
ipcs — report XSI interprocess communication facilities status
ipcs [-qms] [-a|-bcopt]
The ipcs utility shall write information about active interprocess communication facilities.
Without options, information shall be written in short format for message queues, shared memory segments, and semaphore sets that are currently active in the system. Otherwise, the information that is displayed is controlled by the options specified.
The ipcs utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
The ipcs utility accepts the following options:
-q        Write information about active message queues.
-m        Write information about active shared memory segments.
-s        Write information about active semaphore sets.
If -q, -m, or -s are specified, only information about those facilities shall be written. If none of these three are specified, information about all three shall be written subject to the following options:
-a        Use all print options. (This is a shorthand notation for -b, -c, -o, -p, and -t.)
-b        Write information on maximum allowable size. (Maximum number of bytes in messages on queue for message queues, size of segments for shared memory, and number of semaphores in each set for semaphores.)
-c        Write creator's user name and group name; see below.
-o        Write information on outstanding usage. (Number of messages on queue and total number of bytes in messages on queue for message queues, and number of processes attached to shared memory segments.)
-p        Write process number information. (Process ID of the last process to send a message and process ID of the last process to receive a message on message queues, process ID of the creating process, and process ID of the last process to attach or detach on shared memory segments.)
-t        Write time information. (Time of the last control operation that changed the access permissions for all facilities, time of the last msgsnd() and msgrcv() operations on message queues, time of the last shmat() and shmdt() operations on shared memory, and time of the last semop() operation on semaphores.)
*  The group database
*  The user database
The following environment variables shall affect the execution of ipcs:
TZ        Determine the timezone for the date and time strings written by ipcs.  If TZ is unset or null, an unspecified default timezone shall be used.
An introductory line shall be written with the format:
"IPC status from %s as of %s\n", <source>, <date>
where <source> indicates the source used to gather the statistics and <date> is the information that would be produced by the date command when invoked in the POSIX locale.
The ipcs utility then shall create up to three reports depending upon the -q, -m, and -s options. The first report shall indicate the status of message queues, the second report shall indicate the status of shared memory segments, and the third report shall indicate the status of semaphore sets.
If the corresponding facility is not installed or has not been used since the last reboot, then the report shall be written out in the format:
"%s facility not in system.\n", <facility>
where <facility> is Message Queue, Shared Memory, or Semaphore, as appropriate. If the facility has been installed and has been used since the last reboot, column headings separated by one or more <space> characters and followed by a <newline> shall be written as indicated below followed by the facility name written out using the format:
"%s:\n", <facility>
where <facility> is Message Queues, Shared Memory, or Semaphores, as appropriate. On the second and third reports the column headings need not be written if the last column headings written already provide column headings for all information in that report.
The column headings provided in the first column below and the meaning of the information in those columns shall be given in order below; the letters in parentheses indicate the options that shall cause the corresponding column to appear; ``all'' means that the column shall always appear. Each column is separated by one or more <space> characters. Note that these options only determine what information is provided for each report; they do not determine which reports are written.
T (all)     Type of facility:
q       Message queue.
m       Shared memory segment.
s       Semaphore.
This field is a single character written using the format %c.
ID (all)    The identifier for the facility entry. This field shall be written using the format %d.
KEY (all)   The key used as an argument to msgget(), semget(), or shmget() to create the facility entry.
Note:     The key of a shared memory segment is changed to IPC_PRIVATE when the segment has been removed until all processes attached to the segment detach it.
This field shall be written using the format 0x%x.
MODE (all)  The facility access modes and flags. The mode shall consist of 11 characters that are interpreted as follows.
The first character shall be:
S       If a process is waiting on a msgsnd() operation.
-       If the above is not true.
The second character shall be:
R       If a process is waiting on a msgrcv() operation.
C or -  If the associated shared memory segment is to be cleared when the first attach operation is executed.
-       If none of the above is true.
The next nine characters shall be interpreted as three sets of three bits each. The first set refers to the owner's permissions; the next to permissions of others in the usergroup of the facility entry; and the last to all others. Within each set, the first character indicates permission to read, the second character indicates permission to write or alter the facility entry, and the last character is a <hyphen-minus> ('-').
The permissions shall be indicated as follows:
r       If read permission is granted.
w       If write permission is granted.
a       If alter permission is granted.
-       If the indicated permission is not granted.
The first character following the permissions specifies if there is an alternate or additional access control method associated with the facility. If there is no alternate or additional access control method associated with the facility, a single <space> shall be written; otherwise, another printable character is written.
OWNER (all) The user name of the owner of the facility entry. If the user name of the owner is found in the user database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the user ID of the owner shall be written using the format %d.
GROUP (all) The group name of the owner of the facility entry. If the group name of the owner is found in the group database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the group ID of the owner shall be written using the format %d.
The following nine columns shall be only written out for message queues:
CREATOR (a,c) The user name of the creator of the facility entry. If the user name of the creator is found in the user database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the user ID of the creator shall be written using the format %d.
CGROUP (a,c) The group name of the creator of the facility entry. If the group name of the creator is found in the group database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the group ID of the creator shall be written using the format %d.
CBYTES (a,o) The number of bytes in messages currently outstanding on the associated message queue. This field shall be written using the format %d.
QNUM (a,o)  The number of messages currently outstanding on the associated message queue. This field shall be written using the format %d.
QBYTES (a,b) The maximum number of bytes allowed in messages outstanding on the associated message queue. This field shall be written using the format %d.
LSPID (a,p) The process ID of the last process to send a message to the associated queue. This field shall be written using the format:
"%d", <pid>
where <pid> is 0 if no message has been sent to the corresponding message queue; otherwise, <pid> shall be the process ID of the last process to send a message to the queue.
LRPID (a,p) The process ID of the last process to receive a message from the associated queue. This field shall be written using the format:
where <pid> is 0 if no message has been received from the corresponding message queue; otherwise, <pid> shall be the process ID of the last process to receive a message from the queue.
STIME (a,t) The time the last message was sent to the associated queue. If a message has been sent to the corresponding message queue, the hour, minute, and second of the last time a message was sent to the queue shall be written using the format %d:%2.2d:%2.2d.  Otherwise, the format " no-entry" shall be written.
RTIME (a,t) The time the last message was received from the associated queue.  If a message has been received from the corresponding message queue, the hour, minute, and second of the last time a message was received from the queue shall be written using the format %d:%2.2d:%2.2d.  Otherwise, the format " no-entry" shall be written.
The following eight columns shall be only written out for shared memory segments.
CREATOR (a,c) The user of the creator of the facility entry. If the user name of the creator is found in the user database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the user ID of the creator shall be written using the format %d.
NATTCH (a,o) The number of processes attached to the associated shared memory segment. This field shall be written using the format %d.
SEGSZ (a,b) The size of the associated shared memory segment. This field shall be written using the format %d.
CPID (a,p)  The process ID of the creator of the shared memory entry. This field shall be written using the format %d.
LPID (a,p)  The process ID of the last process to attach or detach the shared memory segment. This field shall be written using the format:
where <pid> is 0 if no process has attached the corresponding shared memory segment; otherwise, <pid> shall be the process ID of the last process to attach or detach the segment.
ATIME (a,t) The time the last attach on the associated shared memory segment was completed. If the corresponding shared memory segment has ever been attached, the hour, minute, and second of the last time the segment was attached shall be written using the format %d:%2.2d:%2.2d.  Otherwise, the format " no- entry" shall be written.
DTIME (a,t) The time the last detach on the associated shared memory segment was completed. If the corresponding shared memory segment has ever been detached, the hour, minute, and second of the last time the segment was detached shall be written using the format %d:%2.2d:%2.2d.  Otherwise, the format " no- entry" shall be written.
The following four columns shall be only written out for semaphore sets:
CGROUP     (a,c) The group name of the creator of the facility entry. If the group name of the creator is found in the group database, at least the first eight column positions of the name shall be written using the format %s.  Otherwise, the group ID of the creator shall be written using the format %d.
NSEMS (a,b) The number of semaphores in the set associated with the semaphore entry. This field shall be written using the format %d.
OTIME (a,t) The time the last semaphore operation on the set associated with the semaphore entry was completed. If a semaphore operation has ever been performed on the corresponding semaphore set, the hour, minute, and second of the last semaphore operation on the semaphore set shall be written using the format %d:%2.2d:%2.2d.  Otherwise, the format " no- entry" shall be written.
The following column shall be written for all three reports when it is requested:
CTIME (a,t) The time the associated entry was created or changed. The hour, minute, and second of the time when the associated entry was created shall be written using the format %d:%2.2d:%2.2d.
Things can change while ipcs is running; the information it gives is guaranteed to be accurate only when it was retrieved.
ipcrm
The System Interfaces volume of POSIX.1‐2017, msgrcv(), msgsnd(), semget(), semop(), shmat(), shmdt(), shmget()
LEGIT:(GIT)                                                          LEGIT:(GIT)
Legit: Git for Humans -
Inspired by GitHub for Mac.
GitHub for Mac is not just a Git client.
This comment on Hacker News says it best: They haven't re-created the git CLI tool in a GUI, they've created something different. They've created a tool that makes Git more accessible. Little things like auto-stashing when you switch branches will confuse git veterans, but it will make Git much easier to grok for newcomers because of the assumptions it makes about your Git workflow.
Why not bring this innovation back to the command line?
switch <branch> Switches to specified branch.  Defaults to current branch. Automatically stashes and unstashes any changes. (alias: sw)
sync [<branch>] Synchronizes the given branch. Defaults to current branch.  Stash, Fetch, Auto-Merge/Rebase, Push, and Unstash.  You can only sync published branches. (alias: sy)
publish [<branch>] Publishes specified branch to the remote. (alias: pub)
unpublish <branch> Removes specified branch from the remote. (alias: unp)
undo   Un-does the last commit in git history.  (alias: un)
branches Display a list of available branches.
[image: https://img.shields.io/pypi/v/legit.svg] [image: https://img.shields.io/travis/kennethreitz/legit.svg] [image: https://img.shields.io/coveralls/github/kennethreitz/legit.svg]
From PyPI with the Python package manager:
pip install legit
Or download a standalone Windows executable from GitHub Releases.
To install the cutting edge version from the git repository:
git clone https://github.com/kennethreitz/legit.git cd legit python setup.py install
Note: if you encountered Permission denied, prepend sudo before the pip or python setup.py command.
You'll then have the wonderful legit command available. Run it within a repository.
To view usage and examples, run legit with no commands or options:
To install the git aliases, run the following command:
legit --install
To uninstall the git aliases, run the following command:
legit --uninstall
All legit commands support --verbose and --fake options.
In order to view the git commands invoked by legit, use the --verbose option:
legit sync --verbose
If you want to see the git commands used by legit but don't want them invoked, use the --fake option:
legit publish --fake
• All remote operations are carried out by the remote identified in $ git config legit.remote remotename
• If a stash pop merge fails, Legit stops. I'd like to add checking for a failed merge, and undo the command with friendly error reporting.
nsnake(6)                         nsnake v3.0.0                        nsnake(6)
nsnake - Classic snake game on the terminal
nsnake [-h] [-v]
nsnake is the classic snake game with textual interface.  You can play it at command-line and uses the nCurses library for graphics.  The rules are the same of any snake game:
You control a hungry snake and the objective is to eat as many fruits you can.  Each fruit eaten increases your size.  The game ends when the snake collides with the walls or itself.
The challenge is to earn the biggest score possible by eating as many fruits as you can.
Controls and game settings can be changed through the in-game menus or by directly editing the settings file.
Default controls: Arrow Keys          Moves the snake
q                   Quits the game at any time
p                   Pauses/Unpauses the game
h                   Show help during the game
-h, --help Displays the quick help text.
-v, --version Displays the version and general information.
$(HOME)/.local/share/nsnake/     Per-user content; game settings and scores
snake4(6)   ktron(6)   yetris(6)
Probably. If you find any, please report it at the issue tracker (https://github.com/alexdantas/nsnake/issue) or email me at <eu@alexdantas.net>.
This manual page and nsnake were both written by Alexandre Dantas <eu@alexdantas.net>.
* http://nsnake.alexdantas.net/
* https://github.com/alexdantas/nsnake/
FILE(1)                    BSD General Commands Manual                   FILE(1)
file — determine file type
file [-bcdEhiklLNnprsSvzZ0] [--apple] [--exclude-quiet] [--extension] [--mime-encoding] [--mime-type] [-e testname] [-F separator] [-f namefile] [-m magicfiles] [-P name=value] file ... file -C [-m magicfiles] file [--help]
This manual page documents version 5.41 of the file command.
file tests each argument in an attempt to classify it.  There are three sets of tests, performed in this order: filesystem tests, magic tests, and language tests.  The first test that succeeds causes the file type to be printed.
The type printed will usually contain one of the words text (the file contains only printing characters and a few common control characters and is probably safe to read on an ASCII terminal), executable (the file contains the result of compiling a program in a form understandable to some UNIX kernel or another), or data meaning anything else (data is usually “binary” or non-printable).  Exceptions are well-known file formats (core files, tar archives) that are known to contain binary data.  When modifying magic files or the program itself, make sure to preserve these keywords. Users depend on knowing that all the readable files in a directory have the word “text” printed.  Don't do as Berkeley did and change “shell commands text” to “shell script”.
The filesystem tests are based on examining the return from a stat(2) system call.  The program checks to see if the file is empty, or if it's some sort of special file.  Any known file types appropriate to the system you are running on (sockets, symbolic links, or named pipes (FIFOs) on those systems that implement them) are intuited if they are defined in the system header file <sys/stat.h>.
The magic tests are used to check for files with data in particular fixed formats.  The canonical example of this is a binary executable (compiled program) a.out file, whose format is defined in <elf.h>, <a.out.h> and possibly <exec.h> in the standard include directory.  These files have a “magic number” stored in a particular place near the beginning of the file that tells the UNIX operating system that the file is a binary executable, and which of several types thereof.  The concept of a “magic number” has been applied by extension to data files.  Any file with some invariant identifier at a small fixed offset into the file can usually be described in this way.  The information identifying these files is read from the compiled magic file /usr/share/file/misc/magic.mgc, or the files in the directory /usr/share/file/misc/magic if the compiled file does not exist. In addition, if $HOME/.magic.mgc or $HOME/.magic exists, it will be used in preference to the system magic files.
If a file does not match any of the entries in the magic file, it is examined to see if it seems to be a text file.  ASCII, ISO-8859-x, non-ISO 8-bit extended-ASCII character sets (such as those used on Macintosh and IBM PC systems), UTF-8-encoded Unicode, UTF-16-encoded Unicode, and EBCDIC character sets can be distinguished by the different ranges and sequences of bytes that constitute printable text in each set.  If a file passes any of these tests, its character set is reported.  ASCII, ISO-8859-x, UTF-8, and extended-ASCII files are identified as “text” because they will be mostly readable on nearly any terminal; UTF-16 and EBCDIC are only “character data” because, while they contain text, it is text that will require translation before it can be read.  In addition, file will attempt to determine other characteristics of text-type files.  If the lines of a file are terminated by CR, CRLF, or NEL, instead of the Unix-standard LF, this will be reported.  Files that contain embedded escape sequences or overstriking will also be identified.
Once file has determined the character set used in a text-type file, it will attempt to determine in what language the file is written.  The language tests look for particular strings (cf.  <names.h>) that can appear anywhere in the first few blocks of a file.  For example, the keyword .br indicates that the file is most likely a troff(1) input file, just as the keyword struct indicates a C program.  These tests are less reliable than the previous two groups, so they are performed last.  The language test routines also test for some miscellany (such as tar(1) archives, JSON files).
Any file that cannot be identified as having been written in any of the character sets listed above is simply said to be “data”.
--apple Causes the file command to output the file type and creator code as used by older MacOS versions.  The code consists of eight letters, the first describing the file type, the latter the creator.  This option works properly only for file formats that have the apple- style output defined.
-b, --brief Do not prepend filenames to output lines (brief mode).
-C, --compile Write a magic.mgc output file that contains a pre-parsed version of the magic file or directory.
-c, --checking-printout Cause a checking printout of the parsed form of the magic file. This is usually used in conjunction with the -m option to debug a new magic file before installing it.
-d      Prints internal debugging information to stderr.
-E      On filesystem errors (file not found etc), instead of handling the error as regular output as POSIX mandates and keep going, issue an error message and exit.
-e, --exclude testname Exclude the test named in testname from the list of tests made to determine the file type.  Valid test names are:
apptype   EMX application type (only on EMX).
ascii     Various types of text files (this test will try to guess the text encoding, irrespective of the setting of the ‘encoding’ option).
encoding  Different text encodings for soft magic tests.
tokens    Ignored for backwards compatibility.
cdf       Prints details of Compound Document Files.
compress  Checks for, and looks inside, compressed files.
csv       Checks Comma Separated Value files.
elf       Prints ELF file details, provided soft magic tests are enabled and the elf magic is found.
json      Examines JSON (RFC-7159) files by parsing them for compliance.
soft      Consults magic files.
tar       Examines tar files by verifying the checksum of the 512 byte tar header.  Excluding this test can provide more detailed content description by using the soft magic method.
text      A synonym for ‘ascii’.
--exclude-quiet Like --exclude but ignore tests that file does not know about. This is intended for compatibility with older versions of file.
--extension Print a slash-separated list of valid extensions for the file type found.
-F, --separator separator Use the specified string as the separator between the filename and the file result returned.  Defaults to ‘:’.
-f, --files-from namefile Read the names of the files to be examined from namefile (one per line) before the argument list.  Either namefile or at least one filename argument must be present; to test the standard input, use ‘-’ as a filename argument.  Please note that namefile is unwrapped and the enclosed filenames are processed when this option is encountered and before any further options processing is done. This allows one to process multiple lists of files with different command line arguments on the same file invocation.  Thus if you want to set the delimiter, you need to do it before you specify the list of files, like: “-F @ -f namefile”, instead of: “-f namefile -F @”.
-h, --no-dereference This option causes symlinks not to be followed (on systems that support symbolic links).  This is the default if the environment variable POSIXLY_CORRECT is not defined.
-i, --mime Causes the file command to output mime type strings rather than the more traditional human readable ones.  Thus it may say ‘text/plain; charset=us-ascii’ rather than “ASCII text”.
--mime-type, --mime-encoding Like -i, but print only the specified element(s).
-k, --keep-going Don't stop at the first match, keep going.  Subsequent matches will be have the string ‘\012- ’ prepended.  (If you want a newline, see the -r option.)  The magic pattern with the highest strength (see the -l option) comes first.
-l, --list Shows a list of patterns and their strength sorted descending by magic(5) strength which is used for the matching (see also the -k option).
-L, --dereference This option causes symlinks to be followed, as the like-named option in ls(1) (on systems that support symbolic links).  This is the default if the environment variable POSIXLY_CORRECT is defined.
-m, --magic-file magicfiles Specify an alternate list of files and directories containing magic.  This can be a single item, or a colon-separated list.  If a compiled magic file is found alongside a file or directory, it will be used instead.
-N, --no-pad Don't pad filenames so that they align in the output.
-n, --no-buffer Force stdout to be flushed after checking each file.  This is only useful if checking a list of files.  It is intended to be used by programs that want filetype output from a pipe.
-p, --preserve-date On systems that support utime(3) or utimes(2), attempt to preserve the access time of files analyzed, to pretend that file never read them.
-P, --parameter name=value Set various parameter limits.
Name         Default    Explanation bytes        1048576    max number of bytes to read from file elf_notes    256        max ELF notes processed elf_phnum    2048       max ELF program sections processed elf_shnum    32768      max ELF sections processed encoding     65536      max number of bytes to scan for encoding evaluation indir        50         recursion limit for indirect magic name         50         use count limit for name/use magic regex        8192       length limit for regex searches
-r, --raw Don't translate unprintable characters to \ooo.  Normally file translates unprintable characters to their octal representation.
-s, --special-files Normally, file only attempts to read and determine the type of argument files which stat(2) reports are ordinary files.  This prevents problems, because reading special files may have peculiar consequences.  Specifying the -s option causes file to also read argument files which are block or character special files.  This is useful for determining the filesystem types of the data in raw disk partitions, which are block special files.  This option also causes file to disregard the file size as reported by stat(2) since on some systems it reports a zero size for raw disk partitions.
-S, --no-sandbox On systems where libseccomp (https://github.com/seccomp/libseccomp) is available, the -S option disables sandboxing which is enabled by default.  This option is needed for file to execute external decompressing programs, i.e. when the -z option is specified and the built-in decompressors are not available.  On systems where sandboxing is not available, this option has no effect.
-v, --version Print the version of the program and exit.
-z, --uncompress Try to look inside compressed files.
-Z, --uncompress-noreport Try to look inside compressed files, but report information about the contents only not the compression.
-0, --print0 Output a null character ‘\0’ after the end of the filename.  Nice to cut(1) the output.  This does not affect the separator, which is still printed.
If this option is repeated more than once, then file prints just the filename followed by a NUL followed by the description (or ERROR: text) followed by a second NUL for each entry.
--help  Print a help message and exit.
The environment variable MAGIC can be used to set the default magic file name.  If that variable is set, then file will not attempt to open $HOME/.magic.  file adds “.mgc” to the value of this variable as appropriate.  The environment variable POSIXLY_CORRECT controls (on systems that support symbolic links), whether file will attempt to follow symlinks or not.  If set, then file follows symlink, otherwise it does not.  This is also controlled by the -L and -h options.
/usr/share/file/misc/magic.mgc  Default compiled list of magic. /usr/share/file/misc/magic      Directory containing default magic files.
file will exit with 0 if the operation was successful or >0 if an error was encountered.  The following errors cause diagnostic messages, but don't affect the program exit code (as POSIX requires), unless -E is specified: •   A file cannot be found •   There is no permission to read a file •   The file type cannot be determined
$ file file.c file /dev/{wd0a,hda} file.c:   C program text file:     ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped /dev/wd0a: block special (0/0) /dev/hda: block special (3/0)
$ file -s /dev/wd0{b,d} /dev/wd0b: data /dev/wd0d: x86 boot sector
$ file -s /dev/hda{,1,2,3,4,5,6,7,8,9,10} /dev/hda:   x86 boot sector /dev/hda1:  Linux/i386 ext2 filesystem /dev/hda2:  x86 boot sector /dev/hda3:  x86 boot sector, extended partition table /dev/hda4:  Linux/i386 ext2 filesystem /dev/hda5:  Linux/i386 swap file /dev/hda6:  Linux/i386 swap file /dev/hda7:  Linux/i386 swap file /dev/hda8:  Linux/i386 swap file /dev/hda9:  empty /dev/hda10: empty
$ file -i file.c file /dev/{wd0a,hda} file.c:      text/x-c file:        application/x-executable /dev/hda:    application/x-not-regular-file /dev/wd0a:   application/x-not-regular-file
hexdump(1), od(1), strings(1), magic(5)
This program is believed to exceed the System V Interface Definition of FILE(CMD), as near as one can determine from the vague language contained therein.  Its behavior is mostly compatible with the System V program of the same name.  This version knows more magic, however, so it will produce different (albeit more accurate) output in many cases.
The one significant difference between this version and System V is that this version treats any white space as a delimiter, so that spaces in pattern strings must be escaped.  For example,
>10     string  language impress        (imPRESS data)
in an existing magic file would have to be changed to
>10     string  language\ impress       (imPRESS data)
In addition, in this version, if a pattern string contains a backslash, it must be escaped.  For example
0       string          \begindata      Andrew Toolkit document
0       string          \\begindata     Andrew Toolkit document
SunOS releases 3.2 and later from Sun Microsystems include a file command derived from the System V one, but with some extensions.  This version differs from Sun's only in minor ways.  It includes the extension of the ‘&’ operator, used as, for example,
>16     long&0x7fffffff >0              not stripped
On systems where libseccomp (https://github.com/seccomp/libseccomp) is available, file is enforces limiting system calls to only the ones necessary for the operation of the program.  This enforcement does not provide any security benefit when file is asked to decompress input files running external programs with the -z option.  To enable execution of external decompressors, one needs to disable sandboxing using the -S option.
The magic file entries have been collected from various sources, mainly USENET, and contributed by various authors.  Christos Zoulas (address below) will collect additional or corrected magic file entries.  A consolidation of magic file entries will be distributed periodically.
The order of entries in the magic file is significant.  Depending on what system you are using, the order that they are put together may be incorrect.  If your old file command uses a magic file, keep the old magic file around for comparison purposes (rename it to /usr/share/file/misc/magic.orig).
There has been a file command in every UNIX since at least Research Version 4 (man page dated November, 1973).  The System V version introduced one significant major change: the external list of magic types.  This slowed the program down slightly but made it a lot more flexible.
This program, based on the System V version, was written by Ian Darwin ⟨ian@darwinsys.com⟩ without looking at anybody else's source code.
John Gilmore revised the code extensively, making it better than the first version.  Geoff Collyer found several inadequacies and provided some magic file entries.  Contributions of the ‘&’ operator by Rob McMahon, ⟨cudcv@warwick.ac.uk⟩, 1989.
Guy Harris, ⟨guy@netapp.com⟩, made many changes from 1993 to the present.
Primary development and maintenance from 1990 to the present by Christos Zoulas ⟨christos@astron.com⟩.
Altered by Chris Lowth ⟨chris@lowth.com⟩, 2000: handle the -i option to output mime type strings, using an alternative magic file and internal logic.
Altered by Eric Fischer ⟨enf@pobox.com⟩, July, 2000, to identify character codes and attempt to identify the languages of non-ASCII files.
Altered by Reuben Thomas ⟨rrt@sc3d.org⟩, 2007-2011, to improve MIME support, merge MIME and non-MIME magic, support directories as well as files of magic, apply many bug fixes, update and fix a lot of magic, improve the build system, improve the documentation, and rewrite the Python bindings in pure Python.
The list of contributors to the ‘magic’ directory (magic files) is too long to include here.  You know who you are; thank you.  Many contributors are listed in the source files.
Copyright (c) Ian F. Darwin, Toronto, Canada, 1986-1999.  Covered by the standard Berkeley Software Distribution copyright; see the file COPYING in the source distribution.
The files tar.h and is_tar.c were written by John Gilmore from his public- domain tar(1) program, and are not covered by the above license.
Please report bugs and send patches to the bug tracker at https://bugs.astron.com/ or the mailing list at ⟨file@astron.com⟩ (visit https://mailman.astron.com/mailman/listinfo/file first to subscribe).
Fix output so that tests for MIME and APPLE flags are not needed all over the place, and actual output is only done in one place.  This needs a design.  Suggestion: push possible outputs on to a list, then pick the last-pushed (most specific, one hopes) value at the end, or use a default if the list is empty.  This should not slow down evaluation.
The handling of MAGIC_CONTINUE and printing \012- between entries is clumsy and complicated; refactor and centralize.
Some of the encoding logic is hard-coded in encoding.c and can be moved to the magic files if we had a !:charset annotation.
Continue to squash all magic bugs.  See Debian BTS for a good source.
Store arbitrarily long strings, for example for %s patterns, so that they can be printed out.  Fixes Debian bug #271672.  This can be done by allocating strings in a string pool, storing the string pool at the end of the magic file and converting all the string pointers to relative offsets from the string pool.
Add syntax for relative offsets after current level (Debian bug #466037).
Make file -ki work, i.e. give multiple MIME types.
Add a zip library so we can peek inside Office2007 documents to print more details about their contents.
Add an option to print URLs for the sources of the file descriptions.
Combine script searches and add a way to map executable names to MIME types (e.g. have a magic value for !:mime which causes the resulting string to be looked up in a table).  This would avoid adding the same magic repeatedly for each new hash-bang interpreter.
When a file descriptor is available, we can skip and adjust the buffer instead of the hacky buffer management we do now.
Fix “name” and “use” to check for consistency at compile time (duplicate “name”, “use” pointing to undefined “name” ).  Make “name” / “use” more efficient by keeping a sorted list of names.  Special-case ^ to flip endianness in the parser so that it does not have to be escaped, and document it.
If the offsets specified internally in the file exceed the buffer size ( HOWMANY variable in file.h), then we don't seek to that offset, but we give up.  It would be better if buffer managements was done when the file descriptor is available so we can seek around the file.  One must be careful though because this has performance and thus security considerations, because one can slow down things by repeateadly seeking.
There is support now for keeping separate buffers and having offsets from the end of the file, but the internal buffer management still needs an overhaul.
You can obtain the original author's latest version by anonymous FTP on ftp.astron.com in the directory /pub/file/file-X.YZ.tar.gz.
GIT-MV(1)                          Git Manual                          GIT-MV(1)
git-mv - Move or rename a file, a directory, or a symlink
git mv <options>... <args>...
Move or rename a file, directory or symlink.
git mv [-v] [-f] [-n] [-k] <source> <destination> git mv [-v] [-f] [-n] [-k] <source> ... <destination directory>
In the first form, it renames <source>, which must exist and be either a file, symlink or directory, to <destination>. In the second form, the last argument has to be an existing directory; the given sources will be moved into this directory.
The index is updated after successful completion, but the change must still be committed.
-f, --force Force renaming or moving of a file even if the target exists
-k Skip move or rename actions which would lead to an error condition. An error happens when a source is neither existing nor controlled by Git, or when it would overwrite an existing file unless -f is given.
-n, --dry-run Do nothing; only show what would happen
-v, --verbose Report the names of files as they are moved.
Moving a submodule using a gitfile (which means they were cloned with a Git version 1.7.8 or newer) will update the gitfile and core.worktree setting to make the submodule work in the new location. It also will attempt to update the submodule.<name>.path setting in the gitmodules(5) file and stage that file (unless -n is used).
Each time a superproject update moves a populated submodule (e.g. when switching between commits before and after the move) a stale submodule checkout will remain in the old location and an empty directory will appear in the new location. To populate the submodule again in the new location the user will have to run "git submodule update" afterwards. Removing the old directory is only safe when it uses a gitfile, as otherwise the history of the submodule will be deleted too. Both steps will be obsolete when recursive submodule update has been implemented.
gdu(1)                                                                    gdu(1)
gdu - Pretty fast disk usage analyzer written in Go
gdu [flags] [directory_to_scan]
Pretty fast disk usage analyzer written in Go.
Gdu is intended primarily for SSD disks where it can fully utilize parallel processing.  However HDDs work as well, but the performance gain is not so huge.
-h, --help[=false] help for gdu
-i, --ignore-dirs=[/proc,/dev,/sys,/run] Absolute paths to ignore (separated by comma)
-I, --ignore-dirs-pattern Absolute path patterns to ignore (separated by comma)
-X, --ignore-from Read absolute path patterns to ignore from file
-l, --log-file="/dev/null" Path to a logfile
-m, --max-cores Set max cores that GDU will use.
-c, --no-color[=false] Do not use colorized output
-x, --no-cross[=false] Do not cross filesystem boundaries
-H, --no-hidden[=false] Ignore hidden directories (beginning with dot)
-n, --non-interactive[=false] Do not run in interactive mode
-p, --no-progress[=false] Do not show progress in non-interactive mode
-s, --summarize[=false] Show only a total in non-interactive mode
-d, --show-disks[=false] Show all mounted disks
-a, --show-apparent-size[=false] Show apparent size
-f, -—input-file Import analysis from JSON file.  If the file is "-", read from standard input.
-o, -—output-file Export all info into file as JSON.  If the file is "-", write to standard output.
-g, --enable-gc[=false] Enable garbage collection during analysis
--enable-profiling[=false] Enable collection of profiling data and provide it on http://localhost:6060/debug/pprof/
-v, --version[=false] Print version
Files and directories may be prefixed by a one-character flag with following meaning:
!      An error occurred while reading this directory.
.      An error occurred while reading a subdirectory, size may be not correct.
@      File is symlink or socket.
H      Same file was already counted (hard link).
e      Directory is empty.
HALT(8)                               halt                               HALT(8)
halt, poweroff, reboot - Halt, power-off or reboot the machine
halt [OPTIONS...]
poweroff [OPTIONS...]
reboot [OPTIONS...]
halt, poweroff, reboot may be used to halt, power-off, or reboot the machine. All three commands take the same options.
The following options are understood:
--help Print a short help text and exit.
--halt Halt the machine, regardless of which one of the three commands is invoked.
-p, --poweroff Power-off the machine, regardless of which one of the three commands is invoked.
--reboot Reboot the machine, regardless of which one of the three commands is invoked.
-f, --force Force immediate halt, power-off, or reboot. When specified once, this results in an immediate but clean shutdown by the system manager. When specified twice, this results in an immediate shutdown without contacting the system manager. See the description of --force in systemctl(1) for more details.
-w, --wtmp-only Only write wtmp shutdown entry, do not actually halt, power-off, reboot.
-d, --no-wtmp Do not write wtmp shutdown entry.
-n, --no-sync Don't sync hard disks/storage media before halt, power-off, reboot.
--no-wall Do not send wall message before halt, power-off, reboot.
On success, 0 is returned, a non-zero failure code otherwise.
These commands are implemented in a way that preserves basic compatibility with the original SysV commands.  systemctl(1) verbs halt, poweroff, reboot provide the same functionality with some additional features.
Note that on many SysV systems halt used to be synonymous to poweroff, i.e. both commands would equally result in powering the machine off. systemd is more accurate here, and halt results in halting the machine only (leaving power on), and poweroff is required to actually power it off.
systemd(1), systemctl(1), shutdown(8), wall(1)
M4(1)                             User Commands                            M4(1)
m4 - macro processor
m4 [OPTION]... [FILE]...
Process macros in FILEs.  If no FILE or if FILE is `-', standard input is read.
Mandatory or optional arguments to long options are mandatory or optional for short options too.
Operation modes: --help display this help and exit
-E, --fatal-warnings once: warnings become errors, twice: stop execution at first error
-i, --interactive unbuffer output, ignore interrupts
-P, --prefix-builtins force a `m4_' prefix to all builtins
-Q, --quiet, --silent suppress some warnings for builtins
--warn-macro-sequence[=REGEXP] warn if macro definition matches REGEXP,
default \$\({[^}]*}\|[0-9][0-9]+\)
-W, --word-regexp=REGEXP use REGEXP for macro name syntax
Preprocessor features: -D, --define=NAME[=VALUE] define NAME as having VALUE, or empty
-I, --include=DIRECTORY append DIRECTORY to include path
-s, --synclines generate `#line NUM "FILE"' lines
-U, --undefine=NAME undefine NAME
Limits control: -g, --gnu override -G to re-enable GNU extensions
-G, --traditional suppress all GNU extensions
-H, --hashsize=PRIME set symbol lookup hash table size [509]
-L, --nesting-limit=NUMBER change nesting limit, 0 for unlimited [0]
Frozen state files: -F, --freeze-state=FILE produce a frozen state on FILE at end
-R, --reload-state=FILE reload a frozen state from FILE at start
Debugging: -d, --debug[=FLAGS] set debug level (no FLAGS implies `aeq')
--debugfile[=FILE] redirect debug and trace output to FILE (default stderr, discard if empty string)
-l, --arglength=NUM restrict macro tracing size
-t, --trace=NAME trace NAME when it is defined
FLAGS is any of: a      show actual arguments
c      show before collect, after collect and after call
e      show expansion
f      say current input file name
i      show changes in input files
l      say current input line number
p      show results of path searches
q      quote values as necessary, with a or e flag
t      trace for all macro calls, not only traceon'ed
x      add a unique macro call id, useful with c flag
V      shorthand for all of the above flags
If defined, the environment variable `M4PATH' is a colon-separated list of directories included after any specified by `-I'.
Exit status is 0 for success, 1 for failure, 63 for frozen file version mismatch, or whatever value was passed to the m4exit macro.
Written by Rene' Seindal.
Report bugs to: bug-m4@gnu.org GNU M4 home page: <https://www.gnu.org/software/m4/> General help using GNU software: <https://www.gnu.org/gethelp/>