neulab/tldr huggingface dataset:
┌────────┬───────┬───────┬────────────┬───────────────────────┐ │Address │ Addr1 │ Addr2 │   Status   │        Comment        │ ├────────┼───────┼───────┼────────────┼───────────────────────┤ │7,      │   7   │   7   │ Historical │                       │ │7,5,    │   5   │   5   │ Historical │                       │ │7,5,9   │   5   │   9   │ Historical │                       │ │7,9     │   7   │   9   │ Historical │                       │ │7,+     │   7   │   8   │ Historical │                       │ │,       │   1   │   $   │ Historical │                       │ │,7      │   1   │   7   │ Extension  │                       │ │,,      │   $   │   $   │ Extension  │                       │ │,;      │   $   │   $   │ Extension  │                       │ │7;      │   7   │   7   │ Historical │                       │ │7;5;    │   5   │   5   │ Historical │                       │ │7;5;9   │   5   │   9   │ Historical │                       │ │7;5,9   │   5   │   9   │ Historical │                       │ │7;$;4   │   $   │   4   │ Historical │ Valid, but erroneous. │ │7;9     │   7   │   9   │ Historical │                       │ │7;+     │   7   │   8   │ Historical │                       │ │;       │   .   │   $   │ Historical │                       │ │;7      │   .   │   7   │ Extension  │                       │ │;;      │   $   │   $   │ Extension  │                       │ │;,      │   $   │   $   │ Extension  │                       │ └────────┴───────┴───────┴────────────┴───────────────────────┘ Historically, ed accepted the '^' character as an address, in which case it was identical to the <hyphen-minus> character. POSIX.1‐2008 does not require or prohibit this behavior.
Section 1.4, Utility Description Defaults, ex, sed, sh, vi
The Base Definitions volume of POSIX.1‐2017, Table 5-1, Escape Sequences and Associated Actions, Chapter 8, Environment Variables, Section 9.3, Basic Regular Expressions, Chapter 11, General Terminal Interface, Section 12.2, Utility Syntax Guidelines
MPSTAT(1)                      Linux User's Manual                     MPSTAT(1)
mpstat - Report processors related statistics.
mpstat [ -A ] [ --dec={ 0 | 1 | 2 } ] [ -n ] [ -u ] [ -T ] [ -V ] [ -I { keyword[,...] | ALL } ] [ -N { node_list | ALL } ] [ -o JSON ] [ -P { cpu_list | ALL } ] [ interval [ count ] ]
The mpstat command writes to standard output activities for each available processor, processor 0 being the first one.  Global average activities among all processors are also reported.  The mpstat command can be used on both SMP and UP machines, but in the latter, only global average activities will be printed. If no activity has been selected, then the default report is the CPU utilization report.
The interval parameter specifies the amount of time in seconds between each report.  A value of 0 (or no parameters at all) indicates that processors statistics are to be reported for the time since system startup (boot). The count parameter can be specified in conjunction with the interval parameter if this one is not set to zero. The value of count determines the number of reports generated at interval seconds apart. If the interval parameter is specified without the count parameter, the mpstat command generates reports continuously.
-A     This option is equivalent to specifying -n -u -I ALL.  This option also implies specifying -N ALL -P ALL unless these options are explicitly set on the command line.
-I { keyword[,...] | ALL } Report interrupts statistics.  Possible keywords are CPU, SCPU, and SUM.
With the CPU keyword, the number of each individual interrupt received per second by the CPU or CPUs is displayed. Interrupts are those listed in /proc/interrupts file.
With the SCPU keyword, the number of each individual software interrupt received per second by the CPU or CPUs is displayed. This option works only with kernels 2.6.31 and later. Software interrupts are those listed in /proc/softirqs file.
With the SUM keyword, the mpstat command reports the total number of interrupts per processor.  The following values are displayed:
CPU    Processor number. The keyword all indicates that statistics are calculated as averages among all processors.
intr/s Show the total number of interrupts received per second by the CPU or CPUs.
The ALL keyword is equivalent to specifying all the keywords above and therefore all the interrupts statistics are displayed.
-N { node_list | ALL } Indicate the NUMA nodes for which statistics are to be reported. node_list is a list of comma-separated values or range of values (e.g., 0,2,4-7,12-). Note that node all is the global average among all nodes. The ALL keyword indicates that statistics are to be reported for all nodes.
-n     Report summary CPU statistics based on NUMA node placement. The following values are displayed:
NODE   Logical NUMA node number. The keyword all indicates that statistics are calculated as averages among all nodes.
All the other fields are the same as those displayed with option -u (see below).
-o JSON Display the statistics in JSON (Javascript Object Notation) format.  JSON output field order is undefined, and new fields may be added in the future.
-P { cpu_list | ALL } Indicate the processors for which statistics are to be reported. cpu_list is a list of comma-separated values or range of values (e.g., 0,2,4-7,12-).  Note that processor 0 is the first processor, and processor all is the global average among all processors.  The ALL keyword indicates that statistics are to be reported for all processors.  Offline processors are not displayed.
-T     Display topology elements in the CPU report (see option -u below). The following elements are displayed:
CORE   Logical core number.
SOCK   Logical socket number.
NODE   Logical NUMA node number.
-u     Report CPU utilization. The following values are displayed:
%usr   Show the percentage of CPU utilization that occurred while executing at the user level (application).
%nice  Show the percentage of CPU utilization that occurred while executing at the user level with nice priority.
%sys   Show the percentage of CPU utilization that occurred while executing at the system level (kernel). Note that this does not include time spent servicing hardware and software interrupts.
%iowait Show the percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request.
%irq   Show the percentage of time spent by the CPU or CPUs to service hardware interrupts.
%soft  Show the percentage of time spent by the CPU or CPUs to service software interrupts.
%steal Show the percentage of time spent in involuntary wait by the virtual CPU or CPUs while the hypervisor was servicing another virtual processor.
%guest Show the percentage of time spent by the CPU or CPUs to run a virtual processor.
%gnice Show the percentage of time spent by the CPU or CPUs to run a niced guest.
%idle  Show the percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.
The mpstat command takes into account the following environment variable:
I=     SGR substring for CPU number.
N=     SGR substring for non-zero statistics values.
Z=     SGR substring for zero values.
S_TIME_FORMAT If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header.  The mpstat command will use the ISO 8601 format (YYYY-MM- DD) instead.  The timestamp will also be compliant with ISO 8601 format.
mpstat 2 5 Display five reports of global statistics among all processors at two second intervals.
mpstat -P ALL 2 5 Display five reports of statistics for all processors at two second intervals.
/proc filesystem must be mounted for the mpstat command to work.
sar(1), pidstat(1), iostat(1), vmstat(8)
GIT-VERIFY-TAG(1)                  Git Manual                  GIT-VERIFY-TAG(1)
git-verify-tag - Check the GPG signature of tags
git verify-tag [--format=<format>] <tag>...
Validates the gpg signature created by git tag.
--raw Print the raw gpg status output to standard error instead of the normal human-readable output.
-v, --verbose Print the contents of the tag object before validating it.
<tag>... SHA-1 identifiers of Git tag objects.
IWCTL(1)                       Linux Connectivity                       IWCTL(1)
iwctl - Internet wireless control utility
iwctl [options ...] [commands ...]
Tool for configuring iwd daemon via D-Bus interface. It supports both an interactive mode and command line mode.
--username, -u Provide username.
--password, -p Provide password.
--passphrase, -P Provide passphrase.
--dont-ask, -v Don't ask for missing credentials.
--help, -h Show help message and exit.
Interactive mode To start an interactive mode and list all available commands do: .. code-block:
$ iwctl [iwd]# help
To connect to a network: .. code-block:
[iwd]# device list [iwd]# station DEVICE scan [iwd]# station DEVICE get-networks [iwd]# station DEVICE connect SSID
Command line mode To list all available commands in command line mode and exit do: .. code-block:
$ iwctl --help
$ iwctl device list $ iwctl station DEVICE scan $ iwctl station DEVICE get-networks $ iwctl --passphrase=PASSPHRASE station DEVICE connect SSID
iwd(8)
Marcel Holtmann <marcel@holtmann.org>
2013-2019 Intel Corporation
GO-BUILD(1)                  General Commands Manual                 GO-BUILD(1)
go-build - compile the packages named by the import paths
go build [-o output] [build flags] [packages]
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results.
If the arguments to build are a list of .go files from a single directory, build treats them as a list of source files specifying a single package.
When compiling packages, build ignores files that end in '_test.go'.
When compiling a single main package, build writes the resulting executable to an output file named after the first source file ('go build ed.go rx.go' writes 'ed' or 'ed.exe') or the source code directory ('go build unix/sam' writes 'sam' or 'sam.exe').  The '.exe' suffix is added when writing a Windows executable.
When compiling multiple packages or a single non-main package, build compiles the packages but discards the resulting object, serving only as a check that the packages can be built.
The -o flag forces build to write the resulting executable or object to the named output file or directory, instead of the default behavior described in the last two paragraphs. If the named output is an existing directory or ends with a slash or backslash, then any resulting executables will be written to that directory.
The -i flag installs the packages that are dependencies of the target. The -i flag is deprecated. Compiled packages are cached automatically.
The build flags are shared by the build, clean, get, install, list, run, and test commands:
-a     force rebuilding of packages that are already up-to-date.
-n     print the commands but do not run them.
-p n   the number of programs, such as build commands or test binaries, that can be run in parallel. The default is GOMAXPROCS, normally the number of CPUs available.
-race  enable data race detection. Supported only on linux/amd64, freebsd/amd64, darwin/amd64, windows/amd64, linux/ppc64le and linux/arm64 (only for 48-bit VMA).
-msan  enable interoperation with memory sanitizer.  Supported only on linux/amd64, linux/arm64 and only with Clang/LLVM as the host C compiler.  On linux/arm64, pie build mode will be used.
-v     print the names of packages as they are compiled.
-work  print the name of the temporary work directory and do not delete it when exiting.
-x     print the commands.
-asmflags '[pattern=]arg list' arguments to pass on each go tool asm invocation.
-buildmode mode build mode to use. See 'go help buildmode' for more.
-compiler name name of compiler to use, as in runtime.Compiler (gccgo or gc)
-gccgoflags 'arg list' arguments to pass on each gccgo compiler/linker invocation
-gcflags 'arg list' arguments to pass on each go tool compile invocation.
-installsuffix suffix a suffix to use in the name of the package installation directory, in order to keep output separate from default builds.  If using the -race flag, the install suffix is automatically set to race or, if set explicitly, has _race appended to it. Likewise for the -msan flag. Using a -buildmode option that requires non-default compile flags has a similar effect.
-ldflags 'flag list' arguments to pass on each go tool link invocation.
-linkshared build code that will be linked against shared libraries previously created with -buildmode=shared.
-mod mode module download mode to use: readonly, vendor, or mod.  By default, if a vendor directory is present and the go version in go.mod is 1.14 or higher, the go command acts as if -mod=vendor were set.  Otherwise, the go command acts as if -mod=readonly were set.  See https://golang.org/ref/mod#build-commands for details.
-modcacherw leave newly-created directories in the module cache read-write instead of making them read-only.
-modfile file in module aware mode, read (and possibly write) an alternate go.mod file instead of the one in the module root directory. A file named "go.mod" must still be present in order to determine the module root directory, but it is not accessed. When -modfile is specified, an alternate go.sum file is also used: its path is derived from the -modfile flag by trimming the ".mod" extension and appending ".sum".
-overlay file read a JSON config file that provides an overlay for build operations.  The file is a JSON struct with a single field, named 'Replace', that maps each disk file path (a string) to its backing file path, so that a build will run as if the disk file path exists with the contents given by the backing file paths, or as if the disk file path does not exist if its backing file path is empty. Support for the -overlay flag has some limitations: importantly, cgo files included from outside the include path must be in the same directory as the Go package they are included from, and overlays will not appear when binaries and tests are run through go run and go test respectively.
-pkgdir dir install and load all packages from dir instead of the usual locations.  For example, when building with a non-standard configuration, use -pkgdir to keep generated packages in a separate location.
-tags tag,list a comma-separated list of build tags to consider satisfied during the build. For more information about build tags, see the description of build constraints in the documentation for the go/build package.  (Earlier versions of Go used a space-separated list, and that form is deprecated but still recognized.)
-trimpath remove all file system paths from the resulting executable. Instead of absolute file system paths, the recorded file names will begin with either "go" (for the standard library), or a module path@version (when using modules), or a plain import path (when using GOPATH).
-toolexec 'cmd args' a program to use to invoke toolchain programs like vet and asm. For example, instead of running asm, the go command will run ‘cmd args /path/to/asm <arguments for asm>’. The TOOLEXEC_IMPORTPATH environment variable will be set, matching ‘go list -f {{.ImportPath}}’ for the package being built.
The -asmflags, -gccgoflags, -gcflags, and -ldflags flags accept a space- separated list of arguments to pass to an underlying tool during the build. To embed spaces in an element in the list, surround it with either single or double quotes. The argument list may be preceded by a package pattern and an equal sign, which restricts the use of that argument list to the building of packages matching that pattern (see 'go help packages' for a description of package patterns). Without a pattern, the argument list applies only to the packages named on the command line. The flags may be repeated with different patterns in order to specify different arguments for different sets of packages. If a package matches patterns given in multiple flags, the latest match on the command line wins.  For example, 'go build -gcflags=-S fmt' prints the disassembly only for package fmt, while 'go build -gcflags=all=-S fmt' prints the disassembly for fmt and all its dependencies.
For more about specifying packages, see go-packages(7). For more about where packages and binaries are installed, see go- gopath(1). For more about calling between Go and C/C++, run 'go help c'.
Note: Build adheres to certain conventions such as those described by 'go help gopath'. Not all projects can follow these conventions, however. Installations that have their own conventions or that use a separate software build system may choose to use lower-level invocations such as 'go tool compile' and 'go tool link' to avoid some of the overheads and design decisions of the build tool.
go-install(1), go-get(1), go-clean(1).
This manual page was written by Michael Stapelberg <stapelberg@debian.org> and is maintained by the Debian Go Compiler Team <team+go-compiler@tracker.debian.org> based on the output of 'go help build' for the Debian project (and may be used by others).
NSENTER(1)                        User Commands                       NSENTER(1)
nsenter - run program in different namespaces
nsenter [options] [program [arguments]]
The nsenter command executes program in the namespace(s) that are specified in the command-line options (described below). If program is not given, then "${SHELL}" is run (default: /bin/sh).
Enterable namespaces are:
mount namespace Mounting and unmounting filesystems will not affect the rest of the system, except for filesystems which are explicitly marked as shared (with mount --make-shared; see /proc/self/mountinfo for the shared flag). For further details, see mount_namespaces(7) and the discussion of the CLONE_NEWNS flag in clone(2).
UTS namespace Setting hostname or domainname will not affect the rest of the system. For further details, see uts_namespaces(7).
IPC namespace The process will have an independent namespace for POSIX message queues as well as System V message queues, semaphore sets and shared memory segments. For further details, see ipc_namespaces(7).
network namespace The process will have independent IPv4 and IPv6 stacks, IP routing tables, firewall rules, the /proc/net and /sys/class/net directory trees, sockets, etc. For further details, see network_namespaces(7).
PID namespace Children will have a set of PID to process mappings separate from the nsenter process. nsenter will fork by default if changing the PID namespace, so that the new program and its children share the same PID namespace and are visible to each other. If --no-fork is used, the new program will be exec’ed without forking. For further details, see pid_namespaces(7).
user namespace The process will have a distinct set of UIDs, GIDs and capabilities. For further details, see user_namespaces(7).
cgroup namespace The process will have a virtualized view of /proc/self/cgroup, and new cgroup mounts will be rooted at the namespace cgroup root. For further details, see cgroup_namespaces(7).
time namespace The process can have a distinct view of CLOCK_MONOTONIC and/or CLOCK_BOOTTIME which can be changed using /proc/self/timens_offsets. For further details, see time_namespaces(7).
Various of the options below that relate to namespaces take an optional file argument. This should be one of the /proc/[pid]/ns/* files described in namespaces(7), or the pathname of a bind mount that was created on one of those files.
-a, --all Enter all namespaces of the target process by the default /proc/[pid]/ns/* namespace paths. The default paths to the target process namespaces may be overwritten by namespace specific options (e.g., --all --mount=[path]).
The user namespace will be ignored if the same as the caller’s current user namespace. It prevents a caller that has dropped capabilities from regaining those capabilities via a call to setns(). See setns(2) for more details.
-t, --target PID Specify a target process to get contexts from. The paths to the contexts specified by pid are:
/proc/pid/ns/mnt the mount namespace
/proc/pid/ns/uts the UTS namespace
/proc/pid/ns/ipc the IPC namespace
/proc/pid/ns/net the network namespace
/proc/pid/ns/pid the PID namespace
/proc/pid/ns/user the user namespace
/proc/pid/ns/cgroup the cgroup namespace
/proc/pid/ns/time the time namespace
/proc/pid/root the root directory
/proc/pid/cwd the working directory respectively
-m, --mount[=file] Enter the mount namespace. If no file is specified, enter the mount namespace of the target process. If file is specified, enter the mount namespace specified by file.
-u, --uts[=file] Enter the UTS namespace. If no file is specified, enter the UTS namespace of the target process. If file is specified, enter the UTS namespace specified by file.
-i, --ipc[=file] Enter the IPC namespace. If no file is specified, enter the IPC namespace of the target process. If file is specified, enter the IPC namespace specified by file.
-n, --net[=file] Enter the network namespace. If no file is specified, enter the network namespace of the target process. If file is specified, enter the network namespace specified by file.
-p, --pid[=file] Enter the PID namespace. If no file is specified, enter the PID namespace of the target process. If file is specified, enter the PID namespace specified by file.
-U, --user[=file] Enter the user namespace. If no file is specified, enter the user namespace of the target process. If file is specified, enter the user namespace specified by file. See also the --setuid and --setgid options.
-C, --cgroup[=file] Enter the cgroup namespace. If no file is specified, enter the cgroup namespace of the target process. If file is specified, enter the cgroup namespace specified by file.
-T, --time[=file] Enter the time namespace. If no file is specified, enter the time namespace of the target process. If file is specified, enter the time namespace specified by file.
-G, --setgid gid Set the group ID which will be used in the entered namespace and drop supplementary groups. nsenter always sets GID for user namespaces, the default is 0.
-S, --setuid uid Set the user ID which will be used in the entered namespace. nsenter always sets UID for user namespaces, the default is 0.
--preserve-credentials Don’t modify UID and GID when enter user namespace. The default is to drops supplementary groups and sets GID and UID to 0.
-r, --root[=directory] Set the root directory. If no directory is specified, set the root directory to the root directory of the target process. If directory is specified, set the root directory to the specified directory.
-w, --wd[=directory] Set the working directory. If no directory is specified, set the working directory to the working directory of the target process. If directory is specified, set the working directory to the specified directory.
-F, --no-fork Do not fork before exec’ing the specified program. By default, when entering a PID namespace, nsenter calls fork before calling exec so that any children will also be in the newly entered PID namespace.
-Z, --follow-context Set the SELinux security context used for executing a new process according to already running process specified by --target PID. (The util-linux has to be compiled with SELinux support otherwise the option is unavailable.)
Eric Biederman <biederm@xmission.com>, Karel Zak <kzak@redhat.com>
clone(2), setns(2), namespaces(7)
The nsenter command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
FIGLET(6)                         Games Manual                         FIGLET(6)
FIGlet - display large characters made up of ordinary screen characters
figlet [ -cklnoprstvxDELNRSWX ] [ -d fontdirectory ] [ -f fontfile ] [ -m layoutmode ] [ -w outputwidth ] [ -C controlfile ] [ -I infocode ] [ message ]
FIGlet prints its input using large characters (called ``FIGcharacters'')made up of ordinary screen characters (called ``sub- characters'').  FIGlet output is generally reminiscent of the sort of ``signatures'' many people like to put at the end of e-mail and UseNet messages.  It is also reminiscent of the output of some banner programs, although it is oriented normally, not sideways.
FIGlet can print in a variety of fonts, both left-to-right and right-to- left, with adjacent FIGcharacters kerned and ``smushed'' together in various ways.  FIGlet fonts are stored in separate files, which can be identified by the suffix ``.flf''.  In systems with UTF-8 support FIGlet may also support TOIlet ``.tlf'' fonts.  Most FIGlet font files will be stored in FIGlet's default font directory.
FIGlet can also use ``control files'', which tell it to map certain input characters to certain other characters, similar to the Unix tr command. Control files can be identified by the suffix ``.flc''.  Most FIGlet control files will be stored in FIGlet's default font directory.
You can store FIGlet fonts and control files in compressed form.  See COMPRESSED FONTS.
Just start up FIGlet (type ``figlet'') and then type whatever you want. Alternatively, pipe a file or the output of another command through FIGlet, or put input on the command line after the options.  See EXAMPLES for other things to do.
FIGlet reads command line options from left to right, and only the last option that affects a parameter has any effect.  Almost every option has an inverse, so that, for example, if FIGlet is customized with a shell alias, all the options are usually still available.
Commonly-used options are -f, -c, -k, -t, -p and -v.
-f fontfile Select the font.  The .flf suffix may be left off of fontfile, in which case FIGlet automatically appends it.  FIGlet looks for the file first in the default font directory and then in the current directory, or, if fontfile was given as a full pathname, in the given directory.  If the -f option is not specified, FIGlet uses the font that was specified when it was compiled.  To find out which font this is, use the -I3 option.
-d fontdirectory Change the default font directory.  FIGlet looks for fonts first in the default directory and then in the current directory.  If the -d option is not specified, FIGlet uses the directory that was specified when it was compiled.  To find out which directory this is, use the -I2 option.
-c -l -r -x     These options handle the justification of FIGlet output.  -c centers the output horizontally.  -l makes the output flush-left. -r makes it flush-right.  -x (default) sets the justification according to whether left-to-right or right-to-left text is selected.  Left-to-right text will be flush-left, while right-to- left text will be flush-right.  (Left-to-right versus right-to- left text is controlled by -L, -R and -X.)
-t -w outputwidth These options control the outputwidth, or the screen width FIGlet assumes when formatting its output.  FIGlet uses the outputwidth to determine when to break lines and how to center the output. Normally, FIGlet assumes 80 columns so that people with wide terminals won't annoy the people they e-mail FIGlet output to.  -t sets the outputwidth to the terminal width.  If the terminal width cannot be determined, the previous outputwidth is retained.  -w sets the outputwidth to the given integer.  An outputwidth of 1 is a special value that tells FIGlet to print each non-space FIGcharacter, in its entirety, on a separate line, no matter how wide it is.
-p -n     These options control how FIGlet handles newlines.  -p puts FIGlet into ``paragraph mode'', which eliminates some unnecessary line breaks when piping a multi-line file through FIGlet.  In paragraph mode, FIGlet treats line breaks within a paragraph as if they were merely blanks between words.  (Specifically, -p causes FIGlet to convert any newline which is not preceded by a newline and not followed by a space character into a blank.)  -n (default) puts FIGlet back to normal, in which every newline FIGlet reads causes it to produce a line break.
-D -E     -D switches to the German (ISO 646-DE) character set.  Turns `[', `\' and `]' into umlauted A, O and U, respectively.  `{', `|' and `}' turn into the respective lower case versions of these.  `~' turns into s-z.  -E turns off -D processing.  These options are deprecated, which means they probably will not appear in the next version of FIGlet.
-C controlfile -N     These options deal with FIGlet controlfiles.  A controlfile is a file containing a list of commands that FIGlet executes each time it reads a character.  These commands can map certain input characters to other characters, similar to the Unix tr command or the FIGlet -D option.  FIGlet maintains a list of controlfiles, which is empty when FIGlet starts up.  -C adds the given controlfile to the list.  -N clears the controlfile list, cancelling the effect of any previous -C.  FIGlet executes the commands in all controlfiles in the list.  See the file figfont.txt, provided with FIGlet, for details on how to write a controlfile.
-s -S -k -W
-o     These options control how FIGlet spaces the FIGcharacters that it outputs.  -s (default) and -S cause ``smushing''.  The FIGcharacters are displayed as close together as possible, and overlapping sub-characters are removed.  Exactly which sub- characters count as ``overlapping'' depends on the font's layoutmode, which is defined by the font's author.  -k causes ``kerning''.  As many blanks as possible are removed between FIGcharacters, so that they touch, but the FIGcharacters are not smushed.  -W makes FIGlet display all FIGcharacters at their full width, which may be fixed or variable, depending on the font.
The difference between -s and -S is that -s will not smush a font whose author specified kerning or full width as the default layoutmode, whereas -S will attempt to do so.
If there is no information in the font about how to smush, or if the -o option is specified, then the FIGcharacters are ``overlapped''.  This means that after kerning, the first subcharacter of each FIGcharacter is removed.  (This is not done if a FIGcharacter contains only one subcharacter.)
-m layoutmode Specifies an explicit layoutmode between 1 and 63.  Smushmodes are explained in figfont.txt, which also provides complete information on the format of a FIGlet font.  For the sake of backward compatibility with versions of FIGlet before 2.2, -m0 is equivalent to -k, -m-1 is equivalent to -W, and -m-2 is equivalent to -s.  The -m switch is normally used only by font designers testing the various layoutmodes with a new font.
-v -I infocode These options print various information about FIGlet, then exit. If several of these options are given on the command line, only the last is executed, and only after all other command-line options have been dealt with.
-v prints version and copyright information, as well as a ``Usage: ...''  line.  -I prints the information corresponding to the given infocode in a consistent, reliable (i.e., guaranteed to be the same in future releases) format.  -I is primarily intended to be used by programs that use FIGlet.  infocode can be any of the following.
-1 Normal operation (default). This infocode indicates that FIGlet should operate normally, not giving any informational printout, printing its input in the selected font.
0 Version and copyright. This is identical to -v.
1 Version (integer). This will print the version of your copy of FIGlet as a decimal integer.  The main version number is multiplied by 10000, the sub-version number is multiplied by 100, and the sub-sub-version number is multiplied by 1.  These are added together, and the result is printed out.  For example, FIGlet 2.2 will print ``20200'' , version 2.2.1 will print ``20201''.  Similarly, version 3.7.2 would print ``30702''. These numbers are guaranteed to be ascending, with later versions having higher numbers.  Note that the first major release of FIGlet, version 2.0, did not have the -I option.
2 Default font directory. This will print the default font directory.  It is affected by the -d option.
3 Font. This will print the name of the font FIGlet would use.  It is affected by the -f option.  This is not a filename; the ``.flf'' suffix is not printed.
4 Output width. This will print the value FIGlet would use for outputwidth, the number of columns wide FIGlet assumes the screen is. It is affected by the -w and -t options.
5 Supported font formats. This will list font formats supported by FIGlet .  Possible formats are ``flf2'' for FIGfont Version 2 .flf files and ``tlf2'' for TOIlet .tlf files.
If infocode is any other positive value, FIGlet will simply exit without printing anything.
-L -R -X     These options control whether FIGlet prints left-to-right or right-to-left.  -L selects left-to-right printing.  -R selects right-to-left printing.  -X (default) makes FIGlet use whichever is specified in the font file.
Once the options are read, if there are any remaining words on the command line, they are used instead of standard input as the source of text.  This feature allows shell scripts to generate large letters without having to dummy up standard input files.
An empty argument, obtained by two sequential quotes, results in a line break.
To use FIGlet with its default settings, simply type
example% figlet
and then type whatever you like.
To change the font, use the -f option, for example,
example% figlet -f script
Use the -c option if you would prefer centered output:
example% figlet -c
We have found that the most common use of FIGlet is making up large text to be placed in e-mail messages.  For this reason, FIGlet defaults to 80 column output.  If you are using a wider terminal, and would like FIGlet to use the full width of your terminal, use the -t option:
example% figlet -t
If you don't want FIGlet to smush FIGcharacters into each other, use the -k option:
example% figlet -k
If figlet gets its input from a file, it is often a good idea to use -p:
example% figlet -p < myfile
Of course, the above can be combined:
example% figlet -ptk -f shadow < anotherfile example% figlet -cf slant
Finally, if you want to have FIGlet take the input from the command line instead of a file:
example% figlet Hello world
Other Things to Try On many systems nice effects can be obtained from the lean font by piping it through tr.  Some you might want to try are the following:
example% figlet -f lean | tr ' _/' ' ()' example% figlet -f lean | tr ' _/' './\\' example% figlet -f lean | tr ' _/' ' //' example% figlet -f lean | tr ' _/' '/  '
Similar things can be done with the block font and many of the other FIGlet fonts.
You can compress the fonts and controlfiles using the zip archiving program.  Place only one font or controlfile in each archive, and rename the archive file (which will have a name ending in .zip) back to .flf or .flc as the case may be.  If you don't rename the file appropriately, FIGlet won't be able to find it.
FIGlet does not care what the filename within the .zip archive is, and will process only the first file.
The .zip format was chosen because tools to create and manipulate it are widely available for free on many platforms.
Here are a few notes about some of the fonts provided with FIGlet.  You can get many other font from the Web site http://www.figlet.org/   This location should also contain the latest version of FIGlet and other related utilities.
The font standard is the basic FIGlet font, used when no other font is specified.  (This default can be changed when FIGlet is compiled on your system.)  The controlfiles 8859-2, 8859-3, 8859-4, and 8859-9 are provided for interpreting those character sets, also known as ISO Latin-2 through Latin-5 respectively.  The character set 8859-1 (ISO Latin-1) is FIGlet's default and requires no special controlfile.
Closely related are the fonts slant, shadow, small, smslant (both small and slanted), smshadow, (both small and shadowed), and big.  These fonts support only Latin-1, except that big supports Greek FIGcharacters as well; the controlfiles frango (for Greek text written in Latin characters, so-called ``frangovlakhika''), and 8859-7 (for mixed Latin/Greek text) are provided.
The ivrit font is a right-to-left font including both Latin and Hebrew FIGcharacters; the Latin characters are those of the standard font.  The available controlfiles are ilhebrew, which maps the letters you get by typing on a U.S. keyboard as if it were a Hebrew keyboard; ushebrew, which makes a reasonable mapping from Latin letters to Hebrew ones; and 8859-8, which supports mixed Latin/Hebrew text.  Warning: FIGlet doesn't support bidirectional text, so everything will come out right-to-left, even Latin letters.
The fonts terminal, digital, and bubble output the input character with some decoration around it (or no decoration, in the case of terminal). The characters coded 128 to 159, which have varying interpretations, are output as-is.  You can use the appropriate controlfiles to process Latin-2, Latin-3, or Latin-4 (but not Latin-5) text, provided your output device has screen or printer fonts that are appropriate for these character sets.
Two script fonts are available: script, which is larger than standard, and smscript, which is smaller.
The font lean is made up solely of `/' and `_' sub-characters; block is a straight (non-leaning) version of it.
The font mini is very small, and especially suitable for e-mail signatures.
The font banner looks like the output of the banner program; it is a capitals and small capitals font that doesn't support the ISO Latin-1 extensions to plain ASCII.  It does, however, support the Japanese katakana syllabary; the controlfile uskata maps the upper-case and lower- case Latin letters into the 48 basic katakana characters, and the controlfile jis0201 handles JIS 0201X (JIS-Roman) mixed Latin and katakana text.  Furthermore, the banner font also supports Cyrillic (Russian) FIGcharacters; the controlfile 8859-5 supports mixed Latin and Cyrillic text, the controlfile koi8r supports the popular KOI8-R mapping of mixed text, and the controlfile moscow supports a sensible mapping from Latin to Cyrillic, compatible with the moscow font (not supplied).
The fonts mnemonic and safemnem support the mnemonic character set documented in RFC 1345.  They implement a large subset of Unicode (over 1800 characters) very crudely, using ASCII-based mnemonic sequences, and are good for getting a quick look at UTF-8 unicode files, using the controlfile utf8.
FIGLET_FONTDIR If $FIGLET_FONTDIR is set, its value is used as a path to search for font files.
file.flf            FIGlet font file file.flc            FIGlet control file
FIGlet's diagnostics are intended to be self-explanatory.  Possible messages are
Usage: ... Out of memory Unable to open font file Not a FIGlet 2 font file Unable to open control file Not a FIGlet 2 control file "-t" is disabled, since ioctl is not fully implemented.
This last message is printed when the -t option is given, but the operating system in use does not include the system call FIGlet uses to determine the terminal width.
FIGlet also prints an explanatory message if the -F option is given on the command line.  The earlier version of FIGlet, version 2.0, listed the available fonts when the -F option was given.  This option has been removed from FIGlet 2.1.  It has been replaced by the figlist script, which is part of the standard FIGlet package.
``FIGlet'' stands for ``Frank, Ian and Glenn's LETters''.  Inspired by Frank's .sig, Glenn wrote (most of) it, and Ian helped.
Most of the standard FIGlet fonts were inspired by signatures on various UseNet articles.  Since typically hundreds of people use the same style of letters in their signatures, it was often not deemed necessary to give credit to any one font designer.
Very little error checking is done on font and control files.  While FIGlet tries to be forgiving of errors, and should (hopefully) never actually crash, using an improperly-formatted file with FIGlet will produce unpredictable output.
FIGlet does not handle format characters in a very intelligent way.  A tab character is converted to a blank, and vertical-tab, form-feed and carriage-return are each converted to a newline.  On many systems, tabs can be handled better by piping files through expand before piping through FIGlet.
FIGlet output is quite ugly if it is displayed in a proportionally-spaced font.  I suppose this is to be expected.
Please report any errors you find in this man page or the program to <info@figlet.org>
You can get many fonts which are not in the basic FIGlet package from the Web site http://www.figlet.org/   It should also contain the latest version of FIGlet and other utilities related to FIGlet.
There is a mailing list for FIGlet for general discussions about FIGlet and a place where you can ask questions or share ideas with other FIGlet users. It is also the place where we will publish news about new fonts, new software updates etc.
To subscribe or unsubscribe from the FIGlet mailing list, please send email to figlet-subscribe@figlet.org or figlet-unsubscribe@figlet.org or visit the following web page: http://www.figlet.org/mailman/listinfo/figlet
Glenn Chappell did most of the work.  You can e-mail him but he is not an e-mail fanatic; people who e-mail Glenn will probably get answers, but if you e-mail his best friend:
Ian Chai, who is an e-mail fanatic, you'll get answers, endless conversation about the mysteries of life, invitations to join some 473 mailing lists and a free toaster.  (Well, ok, maybe not the free toaster.)
Frank inspired this whole project with his .sig, but don't e-mail him; he's decidedly an un-e-mail-fanatic.
Gilbert "The Mad Programmer" Healton added the -A option for version 2.1.1.  This option specified input from the command line; it is still allowed, but has no effect.
John Cowan added the -o, -s, -k, -S, and -W options, and the support for Unicode mapping tables, ISO 2022/HZ/Shift-JIS/UTF-8 input, and compressed fonts and control files.  He also revised this documentation, with a lot of input from Paul Burton.
Claudio Matsuoka added the support for .tlf files for version 2.2.4 and performs random hacks and bugfixes.
As a fan of FIGlet, Christiaan Keet revised the official FIGlet documentation and set up the new FIGlet website at http://www.figlet.org/ (and the corresponding ftp://ftp.figlet.org/pub/figlet/)
figlist(6), chkfont(6), showfigfonts(6), toilet(1)
GIT-BRV(1)                         Git Extras                         GIT-BRV(1)
git-brv - List branches sorted by their last commit date
git-brv
Pretty listing of branches sorted by the date of their last commit.
Simply run git brv
$ git brv 2020-01-14 adds-git-brv fork/adds-git-brv 1ca0d76 Fixes #700: Adds git-brv 2020-01-08 master       origin/master     265b03e Merge pull request #816 from spacewander/git-sed-pathspec
Written by Ã˜sse <https://github.com/Osse>
dash [-aCefnuvxIimqVEb] [+aCefnuvxIimqVEb] [-o option_name] [+o option_name] [command_file [argument ...]] dash -c [-aCefnuvxIimqVEb] [+aCefnuvxIimqVEb] [-o option_name] [+o option_name] command_string [command_name [argument ...]] dash -s [-aCefnuvxIimqVEb] [+aCefnuvxIimqVEb] [-o option_name] [+o option_name] [argument ...]
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.
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.
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.
Flow-Control Constructs -- if, while, for, case The syntax of the if command is
WABT(1)                    BSD General Commands Manual                   WABT(1)
wasm2wat â€” translate from the binary format to the text format
wasm2wat [options] file
wasm2wat does the inverse of wat2wasm, translate from the binary format back to the text format (also known as a .wat).
-v, --verbose Use multiple times for more info
--help  Print a help message
-o, --output=FILENAME Output file for the generated wast file, by default use stdout
-f, --fold-exprs Write folded expressions where possible
--enable-exceptions Experimental exception handling
--disable-mutable-globals Import/export mutable globals
--enable-saturating-float-to-int Saturating float-to-int operators
--enable-sign-extension Sign-extension operators
--enable-simd SIMD support
--enable-threads Threading support
--inline-exports Write all exports inline
--inline-imports Write all imports inline
--no-debug-names Ignore debug names in the binary file
--generate-names Give auto-generated names to non-named functions, types, etc.
--no-check Don't check for invalid modules
Parse binary file test.wasm and write text file test.wast
$ wasm2wat test.wasm -o test.wat
Parse test.wasm, write test.wat, but ignore the debug names, if any
$ wasm2wat test.wasm --no-debug-names -o test.wat
wasm-interp(1), wasm-objdump(1), wasm-opcodecnt(1), wasm-strip(1), wasm-validate(1), wasm2c(1), wast2json(1), wat-desugar(1), wat2wasm(1), spectest-interp(1)
If you find a bug, please report it at https://github.com/WebAssembly/wabt/issues
ID(1P)                      POSIX Programmer's Manual                     ID(1P)
id — return user identity
id [user]
id -G [-n] [user]
id -g [-nr] [user]
id -u [-nr] [user]
If no user operand is provided, the id utility shall write the user and group IDs and the corresponding user and group names of the invoking process to standard output. If the effective and real IDs do not match, both shall be written. If multiple groups are supported by the underlying system (see the description of {NGROUPS_MAX} in the System Interfaces volume of POSIX.1‐2017), the supplementary group affiliations of the invoking process shall also be written.
If a user operand is provided and the process has appropriate privileges, the user and group IDs of the selected user shall be written. In this case, effective IDs shall be assumed to be identical to real IDs. If the selected user has more than one allowable group membership listed in the group database, these shall be written in the same manner as the supplementary groups described in the preceding paragraph.
The id utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-G        Output all different group IDs (effective, real, and supplementary) only, using the format "%u\n".  If there is more than one distinct group affiliation, output each such affiliation, using the format " %u", before the <newline> is output.
-g        Output only the effective group ID, using the format "%u\n".
-n        Output the name in the format "%s" instead of the numeric ID using the format "%u".
-r        Output the real ID instead of the effective ID.
-u        Output only the effective user ID, using the format "%u\n".
user      The login name for which information is to be written.
The following environment variables shall affect the execution of id:
The following formats shall be used when the LC_MESSAGES locale category specifies the POSIX locale. In other locales, the strings uid, gid, euid, egid, and groups may be replaced with more appropriate strings corresponding to the locale.
"uid=%u(%s) gid=%u(%s)\n", <real user ID>, <user-name>, <real group ID>, <group-name>
If the effective and real user IDs do not match, the following shall be inserted immediately before the '\n' character in the previous format:
" euid=%u(%s)"
with the following arguments added at the end of the argument list:
<effective user ID>, <effective user-name>
If the effective and real group IDs do not match, the following shall be inserted directly before the '\n' character in the format string (and after any addition resulting from the effective and real user IDs not matching):
" egid=%u(%s)"
<effective group-ID>, <effective group name>
If the process has supplementary group affiliations or the selected user is allowed to belong to multiple groups, the first shall be added directly before the <newline> in the format string:
" groups=%u(%s)"