neulab/tldr huggingface dataset:
--mknodes Also checks the LVM special files in /dev that are needed for active LVs and creates any missing ones and removes unused ones.
--notifydbus Send a notification to D-Bus. The command will exit with an error if LVM is not built with support for D-Bus notification, or if the notify_dbus config setting is disabled.
RADARE2(1)                 BSD General Commands Manual                RADARE2(1)
radare2 â€” Advanced command-line hexadecimal editor, disassembler and debugger
radare2 [-a arch] [-b bits] [-B baddr] [-c cmd] [-e k=v] [-i file] [-I prefile] [-k kernel] [-m addr] [-p project] [-P patch] [-r rarun2] [-R rr2rule] [-s addr] [-0AdDwntLquvVxX] -|--|=|file
radare2 is a command-line hexadecimal editor.
"r2" is the alias program name for radare2.
This manpage is not updated yet. Feel free to contribute.
--          Open radare2 on an empty file
-           Equivalent of 'r2 malloc://512'
-0          Print \x00 after initialization and after every command executed
-2          Close stderr before starting RCore
-a arch     force asm.arch (x86, ppc, arm, mips, bf, java, ...)
-A          run 'aaa' command before prompt or patch to analyze all referenced code. Use -AA to run aaaa
-b bits     force asm.bits (16, 32, 64)
-B baddr    Specify the base address to be used when loading a new binary. See 'e?bin.baddr'
-c cmd      Execute the given command before giving prompt
-d          Start in debugger mode
-D dbg.backend Enable debug mode. Set cfg.debug=true
-e k=v      Set configuration eval variable key=value. For example -e scr.color=false
-f          Blocksize = file size
-i file     Run script file. After the file is loaded
-I file     Run script file. Before the file is loaded
-k kernel   Select kernel (asm.os) for syscall resolution
-l plugfile Load given plugin file
-L          List supported IO plugins.
-m addr     map file at given address
-M          Disable demangling
-n          Do not perform any analysis (r_bin). Just load the raw file
-nn         Only load the rbin structures (elf, mach0, ...)
-N          Do not load user settings/projects from ~/.radare2rc, ~/.config/radare2/radare2rc and the scripts inside .../radare2rc.d/ directory.
-NN         Same as -N but also disables the automatic loading of plugins on startup time
-q          Quiet mode (no prompt) and quit after running the commands specified with -i or -c
-qq         Quit before showing the prompt. Right after all the -e -c and -i arguments are evaluated.
-Q          Same as q, but exiting without freeing RCore, this produces leaks at exit time, but saves some precious ms to run the testsuite in fast mode.
-p prj      Set project file
-P file     Apply rapatch file and quit (see doc/rapatch.md for more details)
-r rarun2   Specify dbg.profile rarun2 profile to use when spawning a program for debugging
-R rarun2-directive Specify custom rarun2 directives without having to create a rarun2 profile
-s addr     Start seeking at this address
-S          Enable sandboxed mode (same as -e cfg.sandbox=true)
-t          Get binary information using a thread
-T          Avoid computing the file hashes
-u          Set bin.filter=false to load rbin info without filtering names
-v          Show version information and exit (Use -qv to get just the version number)
-V          Show radare2 library versions
-w          Open in write mode
-h          Show help message
-H          Show files and environment help
-x          Open the file map without executable permissions
-X          Same as -e bin.usextr=false, do not use extract plugins, useful for dyldcache
Type '?' for help
To enter visual mode use the 'V' command. Then press '?' for help
In r2 the debugger commands are implemented under the 'd' command. Type 'd?' for help
R2_CFG_NEWSHELL sets cfg.newshell=true R2_IGNVER     load plugins ignoring the specified version. (be careful) R2_DEBUG      if defined, show error messages and crash signal R2_DEBUG_ASSERT=1 set a breakpoint when hitting an assert R2_MAGICPATH /Users/pancake/.local/share/radare2/share/radare2/4.5.0-git/magic R2_NOPLUGINS do not load r2 shared plugins R2_RCFILE    ~/.radare2rc (user preferences, batch script) R2_RDATAHOME /usr/local FILE path to the current working file.
r2r(1), rahash2(1), rafind2(1), rabin2(1), radiff2(1), rasm2(1), rax2(1), ravc2(1), ragg2(1), rarun2(1),
pancake <pancake@nopcode.org>
IOPING(1)                         User Commands                        IOPING(1)
ioping - simple disk I/O latency monitoring tool
ioping [-ABCDJLRWGYykq] [-a count] [-c count] [-i interval] [-l speed] [-r rate] [-t time] [-T time] [-s size] [-S wsize] [-o offset] [-w deadline] [-p period] [-P period] directory|file|device ioping -h | -v
This tool generates various I/O patterns and lets you monitor I/O speed and latency in real time.
-a, -warmup count Ignore in statistics first count requests, default 1.
-c, -count count Stop after count requests, default 0 (infinite).
-i, -interval time Set time between requests, default 1s.
-l, -speed-limit size Set speed limit in size per second. Increases interval to request- size / speed.
-r, -rate-limit count Set rate limit in count per second. Increases interval to 1 / rate.
-t, -min-time time Minimal valid request time (0us).  Too fast requests are ignored in statistics.
-T, -max-time time Maximum valid request time.  Too slow requests are ignored in statistics.
-s, -size size Request size, default 4k.
-S, -work-size size Working set size (1m for directory, whole size for file or device).
-o, -work-offset size Starting offset in the file/device (0).
-w, -work-time time Stop after time passed, default 0 (infinite).
-p, -print-count count Print raw statistics for every count requests (see format below).
-P, -print-interval time Print raw statistics for every time.
-A, -async Use asynchronous I/O (io_setup(2), io_submit(2) etc syscalls).
-B, -batch Batch mode. Be quiet and print final statistics in raw format.
-C, -cached Use cached I/O. Suppress cache invalidation via posix_fadvise(2)) before read and fdatasync(2) after each write.
-D, -direct Use direct I/O (see O_DIRECT in open(2)).
-J, -json Print output in JSON format.
-L, -linear Use sequential operations rather than random. This also sets default request size to 256k (as in -size 256k).
-R, -rapid Disk seek rate test, or bandwidth test if used together with -linear.
This option suppress human-readable output for each request (as -quiet), sets default interval to zero (-interval 0), stops measurement after 3 seconds (-work-time 3) and increases default working set size to 64m (-work-size 64m).  Working set (-work- size) should be increased accordingly if disk has huge hardware cache.
-W, -write Use writes rather than reads. Safe for temporary file in directory target.  Write I/O gives more reliable results for systems where non-cached reads are not supported or cached at some level.
Might be *DANGEROUS* for file/device: it will shred your data.  In this case should be repeated three times (-WWW).
-G, -read-write Alternate read and write requests.
-Y, -sync Use sync I/O (see O_SYNC in open(2)).
-y, -dsync Use data sync I/O (see O_DSYNC in open(2)).
-k, -keep Keep and reuse temporary working file "ioping.tmp" (only for directory target).
-q, -quiet Suppress periodical human-readable output.
-h, -help Display help message and exit.
-v, -version Display version and exit.
Argument suffixes For options that expect time argument (-interval, -print-interval and -work-time), default is seconds, unless you specify one of the following suffixes (case-insensitive):
ns, nsec nanoseconds (a billionth of a second, 1 / 1 000 000 000)
us, usec microseconds (a millionth of a second, 1 / 1 000 000)
ms, msec milliseconds (a thousandth of a second, 1 / 1 000)
s, sec seconds
m, min minutes
h, hour hours
For options that expect "size" argument (-size, -speed-limit, -work-size and -work-offset), default is bytes, unless you specify one of the following suffixes (case-insensitive):
sector disk sectors (a sector is always 512).
KiB, k, kb kilobytes (1 024 bytes)
page   memory pages (a page is always 4KiB).
MiB, m, mb megabytes (1 048 576 bytes)
GiB, g, gb gigabytes (1 073 741 824 bytes)
TiB, t, tb terabytes (1 099 511 627 776 bytes)
For options that expect "number" argument (-count and -print-count) you can optionally specify one of the following suffixes (case-insensitive):
k      kilo (thousands, 1 000)
m      mega (millions, 1 000 000)
g      giga (billions, 1 000 000 000)
t      tera (trillions, 1 000 000 000 000)
Returns 0 upon success. The following error codes are defined:
1      Invalid usage (error in arguments).
2      Error during preparation stage.
3      Error during runtime.
ioping -print-count 100 -count 200 -interval 0 -quiet . 99 10970974 9024 36961531 90437 110818 358872 30756 100 12516420 100 9573265 10446 42785821 86849 95733 154609 10548 100 10649035 (1) (2)     (3)   (4)      (5)   (6)   (7)    (8)   (9) (10)
(1) count of requests in statistics (2) running time         (nanoseconds) (3) requests per second  (iops) (4) transfer speed       (bytes per second) (5) minimal request time (nanoseconds) (6) average request time (nanoseconds) (7) maximum request time (nanoseconds) (8) request time standard deviation (nanoseconds) (9) total requests       (including warmup, too slow or too fast) (10) total running time  (nanoseconds)
ioping . Show disk I/O latency using the default values and the current directory, until interrupted. This command prepares temporary (unlinked/hidden) working file and reads random chunks from it using non-cached read requests.
ioping -c 10 -s 1M /tmp Measure latency on /tmp using 10 requests of 1 megabyte each.
ioping -R /dev/sda Measure disk seek rate.
ioping -RL /dev/sda Measure disk sequential speed.
ioping -RLB . | awk '{print $4}' Get disk sequential speed in bytes per second.
iostat(1), dd(1), fio(1), stress(1), stress-ng(1), dbench(1), sysbench(1), fsstress, xfstests, hdparm(8), badblocks(8),
⟨https://github.com/koct9i/ioping/⟩.
This program was written by Konstantin Khlebnikov ⟨koct9i@gmail.com⟩. Man-page was written by Kir Kolyshkin ⟨kir@openvz.org⟩.
LXTERMINAL(1)                    http://LXDE.org                   LXTERMINAL(1)
lxterminal - a lightweight terminal emulator based on GTK+ for the LXDE desktop.
lxterminal [options...]
This manual page documents briefly the lxterminal command.
lxterminal is a program that provides a terminal emulator for the desktop, usually for LXDE.
This program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below.
-e STRING --command=STRING --command STRING This option specifies the program (and its command line arguments) to be run in the terminal. Except in the --command= form, this must be the last option on the command line.
--geometry=CHARACTERSxLINES Set the terminal's size in characters and lines.
-l --loginshell Executes login shell.
-t NAME[,NAME[,NAME[...]]] --title=NAME[,NAME[,NAME[...]]] --tabs=NAME[,NAME[,NAME[...]]] Set the terminal's title. Use comma for multiple tabs.
--working-directory=DIRECTORY Set the terminal's working directory.
This manual page was written by paulliu <grandpaul@gmail.com> for the Debian system (but may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 any later version published by the Free Software Foundation.
Ying-Chun Liu Author.
The configuration file can be found in ~/.config/lxterminal/lxterminal.conf.
Copyright Â© 2008 paulliu
docker-commit - Create a new image from a container's changes
docker commit [OPTIONS] CONTAINER [REPOSITORY[:TAG]]
Alias for docker container commit.
-a, --author=""      Author (e.g., "John Hannibal Smith hannibal@a- team.com ⟨mailto:hannibal@a-team.com⟩")
-c, --change=      Apply Dockerfile instruction to the created image
-h, --help[=false]      help for commit
-m, --message=""      Commit message
-p, --pause[=true]      Pause container during commit
DASH(1)                    BSD General Commands Manual                   DASH(1)
dash — command interpreter (shell)
dash [-aCefnuvxIimqVEbp] [+aCefnuvxIimqVEbp] [-o option_name] [+o option_name] [command_file [argument ...]] dash -c [-aCefnuvxIimqVEbp] [+aCefnuvxIimqVEbp] [-o option_name] [+o option_name] command_string [command_name [argument ...]] dash -s [-aCefnuvxIimqVEbp] [+aCefnuvxIimqVEbp] [-o option_name] [+o option_name] [argument ...]
dash is the standard command interpreter for the system.  The current version of dash is in the process of being changed to conform with the POSIX 1003.2 and 1003.2a specifications for the shell.  This version has many features which make it appear similar in some respects to the Korn shell, but it is not a Korn shell clone (see ksh(1)).  Only features designated by POSIX, plus a few Berkeley extensions, are being incorporated into this shell.  This man page is not intended to be a tutorial or a complete specification of the shell.
Overview The shell is a command that reads lines from either a file or the terminal, interprets them, and generally executes other commands.  It is the program that is running when a user logs into the system (although a user can select a different shell with the chsh(1) command).  The shell implements a language that has flow control constructs, a macro facility that provides a variety of features in addition to data storage, along with built in history and line editing capabilities.  It incorporates many features to aid interactive use and has the advantage that the interpretative language is common to both interactive and non-interactive use (shell scripts). That is, commands can be typed directly to the running shell or can be put into a file and the file can be executed directly by the shell.
Invocation If no args are present and if the standard input of the shell is connected to a terminal (or if the -i flag is set), and the -c option is not present, the shell is considered an interactive shell.  An interactive shell generally prompts before each command and handles programming and command errors differently (as described below).  When first starting, the shell inspects argument 0, and if it begins with a dash ‘-’, the shell is also considered a login shell.  This is normally done automatically by the system when the user first logs in.  A login shell first reads commands from the files /etc/profile and .profile if they exist.  If the environment variable ENV is set on entry to an interactive shell, or is set in the .profile of a login shell, the shell next reads commands from the file named in ENV.  Therefore, a user should place commands that are to be executed only at login time in the .profile file, and commands that are executed for every interactive shell inside the ENV file.  To set the ENV variable to some file, place the following line in your .profile of your home directory
ENV=$HOME/.shinit; export ENV
substituting for “.shinit” any filename you wish.
If command line arguments besides the options have been specified, then the shell treats the first argument as the name of a file from which to read commands (a shell script), and the remaining arguments are set as the positional parameters of the shell ($1, $2, etc).  Otherwise, the shell reads commands from its standard input.
Argument List Processing All of the single letter options that have a corresponding name can be used as an argument to the -o option.  The set -o name is provided next to the single letter option in the description below.  Specifying a dash “-” turns the option on, while using a plus “+” disables the option.  The following options can be set from the command line or with the set builtin (described later).
-a allexport     Export all variables assigned to.
-c               Read commands from the command_string operand instead of from the standard input.  Special parameter 0 will be set from the command_name operand and the positional parameters ($1, $2, etc.) set from the remaining argument operands.
-C noclobber     Don't overwrite existing files with “>”.
-e errexit       If not interactive, exit immediately if any untested command fails.  The exit status of a command is considered to be explicitly tested if the command is used to control an if, elif, while, or until; or if the command is the left hand operand of an “&&” or “||” operator.
-f noglob        Disable pathname expansion.
-n noexec        If not interactive, read commands but do not execute them.  This is useful for checking the syntax of shell scripts.
-u nounset       Write a message to standard error when attempting to expand a variable that is not set, and if the shell is not interactive, exit immediately.
-v verbose       The shell writes its input to standard error as it is read.  Useful for debugging.
-x xtrace        Write each command to standard error (preceded by a ‘+ ’) before it is executed.  Useful for debugging.
-I ignoreeof     Ignore EOF's from input when interactive.
-i interactive   Force the shell to behave interactively.
-l               Make dash act as if it had been invoked as a login shell.
-m monitor       Turn on job control (set automatically when interactive).
-s stdin         Read commands from standard input (set automatically if no file arguments are present).  This option has no effect when set after the shell has already started running (i.e. with set).
-V vi            Enable the built-in vi(1) command line editor (disables -E if it has been set).
-E emacs         Enable the built-in emacs(1) command line editor (disables -V if it has been set).
-b notify        Enable asynchronous notification of background job completion.  (UNIMPLEMENTED for 4.4alpha)
-p priviliged    Do not attempt to reset effective uid if it does not match uid. This is not set by default to help avoid incorrect usage by setuid root programs via system(3) or popen(3).
Lexical Structure The shell reads input in terms of lines from a file and breaks it up into words at whitespace (blanks and tabs), and at certain sequences of characters that are special to the shell called “operators”.  There are two types of operators: control operators and redirection operators (their meaning is discussed later).  Following is a list of operators:
Control operators: & && ( ) ; ;; | || <newline>
Redirection operators: < > >| << >> <& >& <<- <>
Quoting Quoting is used to remove the special meaning of certain characters or words to the shell, such as operators, whitespace, or keywords.  There are three types of quoting: matched single quotes, matched double quotes, and backslash.
Backslash A backslash preserves the literal meaning of the following character, with the exception of ⟨newline⟩.  A backslash preceding a ⟨newline⟩ is treated as a line continuation.
Single Quotes Enclosing characters in single quotes preserves the literal meaning of all the characters (except single quotes, making it impossible to put single- quotes in a single-quoted string).
Double Quotes Enclosing characters within double quotes preserves the literal meaning of all characters except dollarsign ($), backquote (`), and backslash (\). The backslash inside double quotes is historically weird, and serves to quote only the following characters: $ ` " \ <newline>. Otherwise it remains literal.
Reserved Words Reserved words are words that have special meaning to the shell and are recognized at the beginning of a line and after a control operator.  The following are reserved words:
!       elif    fi      while   case else    for     then    {       } do      done    until   if      esac
Their meaning is discussed later.
Aliases An alias is a name and corresponding value set using the alias(1) builtin command.  Whenever a reserved word may occur (see above), and after checking for reserved words, the shell checks the word to see if it matches an alias.  If it does, it replaces it in the input stream with its value. For example, if there is an alias called “lf” with the value “ls -F”, then the input:
lf foobar ⟨return⟩
would become
ls -F foobar ⟨return⟩
Aliases provide a convenient way for naive users to create shorthands for commands without having to learn how to create functions with arguments. They can also be used to create lexically obscure code.  This use is discouraged.
Commands The shell interprets the words it reads according to a language, the specification of which is outside the scope of this man page (refer to the BNF in the POSIX 1003.2 document).  Essentially though, a line is read and if the first word of the line (or after a control operator) is not a reserved word, then the shell has recognized a simple command.  Otherwise, a complex command or some other special construct may have been recognized.
Simple Commands If a simple command has been recognized, the shell performs the following actions:
1.   Leading words of the form “name=value” are stripped off and assigned to the environment of the simple command.  Redirection operators and their arguments (as described below) are stripped off and saved for processing.
2.   The remaining words are expanded as described in the section called “Expansions”, and the first remaining word is considered the command name and the command is located.  The remaining words are considered the arguments of the command.  If no command name resulted, then the “name=value” variable assignments recognized in item 1 affect the current shell.
3.   Redirections are performed as described in the next section.
Redirections Redirections are used to change where a command reads its input or sends its output.  In general, redirections open, close, or duplicate an existing reference to a file.  The overall format used for redirection is:
[n] redir-op file
where redir-op is one of the redirection operators mentioned previously. Following is a list of the possible redirections.  The [n] is an optional number between 0 and 9, as in ‘3’ (not ‘[3]’), that refers to a file descriptor.
[n]> file   Redirect standard output (or n) to file.
[n]>| file  Same, but override the -C option.
[n]>> file  Append standard output (or n) to file.
[n]< file   Redirect standard input (or n) from file.
[n1]<&n2    Copy file descriptor n2 as stdout (or fd n1).  fd n2.
[n]<&-      Close standard input (or n).
[n1]>&n2    Copy file descriptor n2 as stdin (or fd n1).  fd n2.
[n]>&-      Close standard output (or n).
[n]<> file  Open file for reading and writing on standard input (or n).
The following redirection is often called a “here-document”.
[n]<< delimiter here-doc-text ... delimiter
All the text on successive lines up to the delimiter is saved away and made available to the command on standard input, or file descriptor n if it is specified.  If the delimiter as specified on the initial line is quoted, then the here-doc-text is treated literally, otherwise the text is subjected to parameter expansion, command substitution, and arithmetic expansion (as described in the section on “Expansions”).  If the operator is “<<-” instead of “<<”, then leading tabs in the here-doc-text are stripped.
Search and Execution There are three types of commands: shell functions, builtin commands, and normal programs – and the command is searched for (by name) in that order. They each are executed in a different way.
When a shell function is executed, all of the shell positional parameters (except $0, which remains unchanged) are set to the arguments of the shell function.  The variables which are explicitly placed in the environment of the command (by placing assignments to them before the function name) are made local to the function and are set to the values given.  Then the command given in the function definition is executed.  The positional parameters are restored to their original values when the command completes.  This all occurs within the current shell.
Shell builtins are executed internally to the shell, without spawning a new process.
Otherwise, if the command name doesn't match a function or builtin, the command is searched for as a normal program in the file system (as described in the next section).  When a normal program is executed, the shell runs the program, passing the arguments and the environment to the program.  If the program is not a normal executable file (i.e., if it does not begin with the "magic number" whose ASCII representation is "#!", so execve(2) returns ENOEXEC then) the shell will interpret the program in a subshell.  The child shell will reinitialize itself in this case, so that the effect will be as if a new shell had been invoked to handle the ad-hoc shell script, except that the location of hashed commands located in the parent shell will be remembered by the child.
Note that previous versions of this document and the source code itself misleadingly and sporadically refer to a shell script without a magic number as a "shell procedure".
Path Search When locating a command, the shell first looks to see if it has a shell function by that name.  Then it looks for a builtin command by that name. If a builtin command is not found, one of two things happen:
1.   Command names containing a slash are simply executed without performing any searches.
2.   The shell searches each entry in PATH in turn for the command.  The value of the PATH variable should be a series of entries separated by colons.  Each entry consists of a directory name.  The current directory may be indicated implicitly by an empty directory name, or explicitly by a single period.
Command Exit Status Each command has an exit status that can influence the behaviour of other shell commands.  The paradigm is that a command exits with zero for normal or success, and non-zero for failure, error, or a false indication.  The man page for each command should indicate the various exit codes and what they mean.  Additionally, the builtin commands return exit codes, as does an executed shell function.
If a command consists entirely of variable assignments then the exit status of the command is that of the last command substitution if any, otherwise 0.
Complex Commands Complex commands are combinations of simple commands with control operators or reserved words, together creating a larger complex command.  More generally, a command is one of the following:
•   simple command
•   pipeline
•   list or compound-list
•   compound command
•   function definition
Unless otherwise stated, the exit status of a command is that of the last simple command executed by the command.
Pipelines A pipeline is a sequence of one or more commands separated by the control operator |.  The standard output of all but the last command is connected to the standard input of the next command.  The standard output of the last command is inherited from the shell, as usual.
The format for a pipeline is:
[!] command1 [| command2 ...]
The standard output of command1 is connected to the standard input of command2.  The standard input, standard output, or both of a command is considered to be assigned by the pipeline before any redirection specified by redirection operators that are part of the command.
If the pipeline is not in the background (discussed later), the shell waits for all commands to complete.
If the reserved word ! does not precede the pipeline, the exit status is the exit status of the last command specified in the pipeline.  Otherwise, the exit status is the logical NOT of the exit status of the last command. That is, if the last command returns zero, the exit status is 1; if the last command returns greater than zero, the exit status is zero.
Because pipeline assignment of standard input or standard output or both takes place before redirection, it can be modified by redirection.  For example:
$ command1 2>&1 | command2
sends both the standard output and standard error of command1 to the standard input of command2.
A ; or ⟨newline⟩ terminator causes the preceding AND-OR-list (described next) to be executed sequentially; a & causes asynchronous execution of the preceding AND-OR-list.
Note that unlike some other shells, each process in the pipeline is a child of the invoking shell (unless it is a shell builtin, in which case it executes in the current shell – but any effect it has on the environment is wiped).
Background Commands – & If a command is terminated by the control operator ampersand (&), the shell executes the command asynchronously – that is, the shell does not wait for the command to finish before executing the next command.
The format for running a command in background is:
command1 & [command2 & ...]
If the shell is not interactive, the standard input of an asynchronous command is set to /dev/null.
Lists – Generally Speaking A list is a sequence of zero or more commands separated by newlines, semicolons, or ampersands, and optionally terminated by one of these three characters.  The commands in a list are executed in the order they are written.  If command is followed by an ampersand, the shell starts the command and immediately proceeds onto the next command; otherwise it waits for the command to terminate before proceeding to the next one.
Short-Circuit List Operators “&&” and “||” are AND-OR list operators.  “&&” executes the first command, and then executes the second command if and only if the exit status of the first command is zero.  “||” is similar, but executes the second command if and only if the exit status of the first command is nonzero.  “&&” and “||” both have the same priority.
Flow-Control Constructs – if, while, for, case The syntax of the if command is
if list then list [ elif list then    list ] ... [ else list ] fi
The syntax of the while command is
while list do   list done
The two lists are executed repeatedly while the exit status of the first list is zero.  The until command is similar, but has the word until in place of while, which causes it to repeat until the exit status of the first list is zero.
The syntax of the for command is
for variable [ in [ word ... ] ] do   list done
The words following in are expanded, and then the list is executed repeatedly with the variable set to each word in turn.  Omitting in word ... is equivalent to in "$@".
The syntax of the break and continue command is
break [ num ] continue [ num ]
Break terminates the num innermost for or while loops.  Continue continues with the next iteration of the innermost loop.  These are implemented as builtin commands.
The syntax of the case command is
case word in [(]pattern) list ;; ... esac
The pattern can actually be one or more patterns (see Shell Patterns described later), separated by “|” characters.  The “(” character before the pattern is optional.
Grouping Commands Together Commands may be grouped by writing either
(list)
{ list; }
The first of these executes the commands in a subshell.  Builtin commands grouped into a (list) will not affect the current shell.  The second form does not fork another shell so is slightly more efficient.  Grouping commands together this way allows you to redirect their output as though they were one program:
{ printf " hello " ; printf " world\n" ; } > greeting
Note that “}” must follow a control operator (here, “;”) so that it is recognized as a reserved word and not as another command argument.
Functions The syntax of a function definition is
name () command
A function definition is an executable statement; when executed it installs a function named name and returns an exit status of zero.  The command is normally a list enclosed between “{” and “}”.
Variables may be declared to be local to a function by using a local command.  This should appear as the first statement of a function, and the syntax is
local [variable | -] ...
Local is implemented as a builtin command.
When a variable is made local, it inherits the initial value and exported and readonly flags from the variable with the same name in the surrounding scope, if there is one.  Otherwise, the variable is initially unset.  The shell uses dynamic scoping, so that if you make the variable x local to function f, which then calls function g, references to the variable x made inside g will refer to the variable x declared inside f, not to the global variable named x.
The only special parameter that can be made local is “-”.  Making “-” local any shell options that are changed via the set command inside the function to be restored to their original values when the function returns.
The syntax of the return command is
return [exitstatus]
It terminates the currently executing function.  Return is implemented as a builtin command.
Variables and Parameters The shell maintains a set of parameters.  A parameter denoted by a name is called a variable.  When starting up, the shell turns all the environment variables into shell variables.  New variables can be set using the form
Variables set by the user must have a name consisting solely of alphabetics, numerics, and underscores - the first of which must not be numeric.  A parameter can also be denoted by a number or a special character as explained below.
Positional Parameters A positional parameter is a parameter denoted by a number (n > 0).  The shell sets these initially to the values of its command line arguments that follow the name of the shell script.  The set builtin can also be used to set or reset them.
Special Parameters A special parameter is a parameter denoted by one of the following special characters.  The value of the parameter is listed next to its character.
*            Expands to the positional parameters, starting from one.  When the expansion occurs within a double-quoted string it expands to a single field with the value of each parameter separated by the first character of the IFS variable, or by a ⟨space⟩ if IFS is unset.
@            Expands to the positional parameters, starting from one.  When the expansion occurs within double-quotes, each positional parameter expands as a separate argument.  If there are no positional parameters, the expansion of @ generates zero arguments, even when @ is double-quoted.  What this basically means, for example, is if $1 is “abc” and $2 is “def ghi”, then "$@" expands to the two arguments:
"abc" "def ghi"
#            Expands to the number of positional parameters.
?            Expands to the exit status of the most recent pipeline.
- (Hyphen.)  Expands to the current option flags (the single-letter option names concatenated into a string) as specified on invocation, by the set builtin command, or implicitly by the shell.
$            Expands to the process ID of the invoked shell.  A subshell retains the same value of $ as its parent.
!            Expands to the process ID of the most recent background command executed from the current shell.  For a pipeline, the process ID is that of the last command in the pipeline.
0 (Zero.)    Expands to the name of the shell or shell script.
Word Expansions This clause describes the various expansions that are performed on words. Not all expansions are performed on every word, as explained later.
Tilde expansions, parameter expansions, command substitutions, arithmetic expansions, and quote removals that occur within a single word expand to a single field.  It is only field splitting or pathname expansion that can create multiple fields from a single word.  The single exception to this rule is the expansion of the special parameter @ within double-quotes, as was described above.
The order of word expansion is:
1.   Tilde Expansion, Parameter Expansion, Command Substitution, Arithmetic Expansion (these all occur at the same time).
2.   Field Splitting is performed on fields generated by step (1) unless the IFS variable is null.
3.   Pathname Expansion (unless set -f is in effect).
4.   Quote Removal.
The $ character is used to introduce parameter expansion, command substitution, or arithmetic evaluation.
Tilde Expansion (substituting a user's home directory) A word beginning with an unquoted tilde character (~) is subjected to tilde expansion.  All the characters up to a slash (/) or the end of the word are treated as a username and are replaced with the user's home directory.  If the username is missing (as in ~/foobar), the tilde is replaced with the value of the HOME variable (the current user's home directory).
Parameter Expansion The format for parameter expansion is as follows:
${expression}
where expression consists of all characters until the matching “}”.  Any “}” escaped by a backslash or within a quoted string, and characters in embedded arithmetic expansions, command substitutions, and variable expansions, are not examined in determining the matching “}”.
The simplest form for parameter expansion is:
${parameter}
The value, if any, of parameter is substituted.
The parameter name or symbol can be enclosed in braces, which are optional except for positional parameters with more than one digit or when parameter is followed by a character that could be interpreted as part of the name. If a parameter expansion occurs inside double-quotes:
1.   Pathname expansion is not performed on the results of the expansion.
2.   Field splitting is not performed on the results of the expansion, with the exception of @.
In addition, a parameter expansion can be modified by using one of the following formats.
${parameter:-word}    Use Default Values.  If parameter is unset or null, the expansion of word is substituted; otherwise, the value of parameter is substituted.
${parameter:=word}    Assign Default Values.  If parameter is unset or null, the expansion of word is assigned to parameter. In all cases, the final value of parameter is substituted.  Only variables, not positional parameters or special parameters, can be assigned in this way.
${parameter:?[word]}  Indicate Error if Null or Unset.  If parameter is unset or null, the expansion of word (or a message indicating it is unset if word is omitted) is written to standard error and the shell exits with a nonzero exit status.  Otherwise, the value of parameter is substituted.  An interactive shell need not exit.
${parameter:+word}    Use Alternative Value.  If parameter is unset or null, null is substituted; otherwise, the expansion of word is substituted.
In the parameter expansions shown previously, use of the colon in the format results in a test for a parameter that is unset or null; omission of the colon results in a test for a parameter that is only unset.
${#parameter}         String Length.  The length in characters of the value of parameter.
The following four varieties of parameter expansion provide for substring processing.  In each case, pattern matching notation (see Shell Patterns), rather than regular expression notation, is used to evaluate the patterns. If parameter is * or @, the result of the expansion is unspecified. Enclosing the full parameter expansion string in double-quotes does not cause the following four varieties of pattern characters to be quoted, whereas quoting characters within the braces has this effect.
${parameter%word}     Remove Smallest Suffix Pattern.  The word is expanded to produce a pattern.  The parameter expansion then results in parameter, with the smallest portion of the suffix matched by the pattern deleted.
${parameter%%word}    Remove Largest Suffix Pattern.  The word is expanded to produce a pattern.  The parameter expansion then results in parameter, with the largest portion of the suffix matched by the pattern deleted.
${parameter#word}     Remove Smallest Prefix Pattern.  The word is expanded to produce a pattern.  The parameter expansion then results in parameter, with the smallest portion of the prefix matched by the pattern deleted.
${parameter##word}    Remove Largest Prefix Pattern.  The word is expanded to produce a pattern.  The parameter expansion then results in parameter, with the largest portion of the prefix matched by the pattern deleted.
Command Substitution Command substitution allows the output of a command to be substituted in place of the command name itself.  Command substitution occurs when the command is enclosed as follows:
$(command)
or (“backquoted” version):
The shell expands the command substitution by executing command in a subshell environment and replacing the command substitution with the standard output of the command, removing sequences of one or more ⟨newline⟩s at the end of the substitution.  (Embedded ⟨newline⟩s before the end of the output are not removed; however, during field splitting, they may be translated into ⟨space⟩s, depending on the value of IFS and quoting that is in effect.)
Arithmetic Expansion Arithmetic expansion provides a mechanism for evaluating an arithmetic expression and substituting its value.  The format for arithmetic expansion is as follows:
$((expression))
The expression is treated as if it were in double-quotes, except that a double-quote inside the expression is not treated specially.  The shell expands all tokens in the expression for parameter expansion, command substitution, and quote removal.
Next, the shell treats this as an arithmetic expression and substitutes the value of the expression.
White Space Splitting (Field Splitting) After parameter expansion, command substitution, and arithmetic expansion the shell scans the results of expansions and substitutions that did not occur in double-quotes for field splitting and multiple fields can result.
The shell treats each character of the IFS as a delimiter and uses the delimiters to split the results of parameter expansion and command substitution into fields.
Pathname Expansion (File Name Generation) Unless the -f flag is set, file name generation is performed after word splitting is complete.  Each word is viewed as a series of patterns, separated by slashes.  The process of expansion replaces the word with the names of all existing files whose names can be formed by replacing each pattern with a string that matches the specified pattern.  There are two restrictions on this: first, a pattern cannot match a string containing a slash, and second, a pattern cannot match a string starting with a period unless the first character of the pattern is a period.  The next section describes the patterns used for both Pathname Expansion and the case command.
Shell Patterns A pattern consists of normal characters, which match themselves, and meta- characters.  The meta-characters are “!”, “*”, “?”, and “[”.  These characters lose their special meanings if they are quoted.  When command or variable substitution is performed and the dollar sign or back quotes are not double quoted, the value of the variable or the output of the command is scanned for these characters and they are turned into meta-characters.
An asterisk (“*”) matches any string of characters.  A question mark matches any single character.  A left bracket (“[”) introduces a character class.  The end of the character class is indicated by a (“]”); if the “]” is missing then the “[” matches a “[” rather than introducing a character class.  A character class matches any of the characters between the square brackets.  A range of characters may be specified using a minus sign.  The character class may be complemented by making an exclamation point the first character of the character class.
To include a “]” in a character class, make it the first character listed (after the “!”, if any).  To include a minus sign, make it the first or last character listed.
Builtins This section lists the builtin commands which are builtin because they need to perform some operation that can't be performed by a separate process. In addition to these, there are several other commands that may be builtin for efficiency (e.g.  printf(1), echo(1), test(1), etc).
true   A null command that returns a 0 (true) exit value.
. file The commands in the specified file are read and executed by the shell.
alias [name[=string ...]] If name=string is specified, the shell defines the alias name with value string.  If just name is specified, the value of the alias name is printed.  With no arguments, the alias builtin prints the names and values of all defined aliases (see unalias).
bg [job] ... Continue the specified jobs (or the current job if no jobs are given) in the background.
command [-p] [-v] [-V] command [arg ...] Execute the specified command but ignore shell functions when searching for it.  (This is useful when you have a shell function with the same name as a builtin command.)
-p     search for command using a PATH that guarantees to find all the standard utilities.
-V     Do not execute the command but search for the command and print the resolution of the command search.  This is the same as the type builtin.
-v     Do not execute the command but search for the command and print the absolute pathname of utilities, the name for builtins or the expansion of aliases.
cd [-LP] [directory] Switch to the specified directory (default HOME).  If an entry for CDPATH appears in the environment of the cd command or the shell variable CDPATH is set and the directory name does not begin with a slash, then the directories listed in CDPATH will be searched for the specified directory.  The format of CDPATH is the same as that of PATH.  If a single dash is specified as the argument, it will be replaced by the value of OLDPWD.  The cd command will print out the name of the directory that it actually switched to if this is different from the name that the user gave.  These may be different either because the CDPATH mechanism was used or because the argument is a single dash.  The -P option causes the physical directory structure to be used, that is, all symbolic links are resolved to their respective values.  The -L option turns off the effect of any preceding -P options.
echo [-n] args... Print the arguments on the standard output, separated by spaces. Unless the -n option is present, a newline is output following the arguments.
If any of the following sequences of characters is encountered during output, the sequence is not output.  Instead, the specified action is performed:
\b      A backspace character is output.
\c      Subsequent output is suppressed.  This is normally used at the end of the last argument to suppress the trailing newline that echo would otherwise output.
\e      Outputs an escape character (ESC).
\f      Output a form feed.
\n      Output a newline character.
\r      Output a carriage return.
\t      Output a (horizontal) tab character.
\v      Output a vertical tab.
\0digits Output the character whose value is given by zero to three octal digits.  If there are zero digits, a nul character is output.
\\      Output a backslash.
All other backslash sequences elicit undefined behaviour.
eval string ... Concatenate all the arguments with spaces.  Then re-parse and execute the command.
exec [command arg ...] Unless command is omitted, the shell process is replaced with the specified program (which must be a real program, not a shell builtin or function).  Any redirections on the exec command are marked as permanent, so that they are not undone when the exec command finishes.
exit [exitstatus] Terminate the shell process.  If exitstatus is given it is used as the exit status of the shell; otherwise the exit status of the preceding command is used.
export name ...
export -p The specified names are exported so that they will appear in the environment of subsequent commands.  The only way to un-export a variable is to unset it.  The shell allows the value of a variable to be set at the same time it is exported by writing
export name=value
With no arguments the export command lists the names of all exported variables.  With the -p option specified the output will be formatted suitably for non-interactive use.
fc [-e editor] [first [last]]
fc -s [old=new] [first] The fc builtin lists, or edits and re-executes, commands previously entered to an interactive shell.
-e editor Use the editor named by editor to edit the commands.  The editor string is a command name, subject to search via the PATH variable.  The value in the FCEDIT variable is used as a default when -e is not specified.  If FCEDIT is null or unset, the value of the EDITOR variable is used.  If EDITOR is null or unset, ed(1) is used as the editor.
-l (ell) List the commands rather than invoking an editor on them. The commands are written in the sequence indicated by the first and last operands, as affected by -r, with each command preceded by the command number.
-n     Suppress command numbers when listing with -l.
-r     Reverse the order of the commands listed (with -l) or edited (with neither -l nor -s).
-s     Re-execute the command without invoking an editor.
last   Select the commands to list or edit.  The number of previous commands that can be accessed are determined by the value of the HISTSIZE variable.  The value of first or last or both are one of the following: