neulab/tldr huggingface dataset:
mkfifo - make FIFOs (named pipes)
mkfifo [OPTION]... NAME...
Create named pipes (FIFOs) with the given NAMEs.
mkfifo(3)
Full documentation <https://www.gnu.org/software/coreutils/mkfifo> or available locally via: info '(coreutils) mkfifo invocation'
exa(1)                                                                    exa(1)
exa — a modern replacement for ls
exa [options] [files...]
exa is a modern replacement for ls.  It uses colours for information by default, helping you distinguish between many types of files, such as whether you are the owner, or in the owning group.
It also has extra features not present in the original ls, such as viewing the Git status for a directory, or recursing into directories with a tree view.
exa    Lists the contents of the current directory in a grid.
exa --oneline --reverse --sort=size Displays a list of files with the largest at the top.
exa --long --header --inode --git Displays a table of files with a header, showing each file’s metadata, inode, and Git status.
exa --long --tree --level=3 Displays a tree of files, three levels deep, as well as each file’s metadata.
-1, --oneline Display one entry per line.
-F, --classify Display file kind indicators next to file names.
-G, --grid Display entries as a grid (default).
-l, --long Display extended file metadata as a table.
-R, --recurse Recurse into directories.
-T, --tree Recurse into directories as a tree.
-x, --across Sort the grid across, rather than downwards.
--color, --colour=WHEN When to use terminal colours.  Valid settings are `always', `automatic', and `never'.
--color-scale, --colour-scale Colour file sizes on a scale.
--icons Display icons next to file names.
--no-icons Don’t display icons.  (Always overrides –icons)
-a, --all Show hidden and “dot” files.  Use this twice to also show the `.' and `..'  directories.
-d, --list-dirs List directories as regular files, rather than recursing and listing their contents.
-L, --level=DEPTH Limit the depth of recursion.
-r, --reverse Reverse the sort order.
-s, --sort=SORT_FIELD Which field to sort by.
Valid sort fields are `name', `Name', `extension', `Extension', `size', `modified', `changed', `accessed', `created', `inode', `type', and `none'.
The modified sort field has the aliases `date', `time', and `newest', and its reverse order has the aliases `age' and `oldest'.
Sort fields starting with a capital letter will sort uppercase before lowercase: `A' then `B' then `a' then `b'.  Fields starting with a lowercase letter will mix them: `A' then `a' then `B' then `b'.
-I, --ignore-glob=GLOBS Glob patterns, pipe-separated, of files to ignore.
--git-ignore [if exa was built with git support] Do not list files that are ignored by Git.
--group-directories-first List directories before other files.
-D, --only-dirs List only directories, not files.
These options are available when running with --long (-l):
-b, --binary List file sizes with binary prefixes.
-B, --bytes List file sizes in bytes, without any prefixes.
--changed Use the changed timestamp field.
-g, --group List each file’s group.
-h, --header Add a header row to each column.
-H, --links List each file’s number of hard links.
-i, --inode List each file’s inode number.
-m, --modified Use the modified timestamp field.
-n, --numeric List numeric user and group IDs.
-S, --blocks List each file’s number of file system blocks.
-t, --time=WORD Which timestamp field to list.  Valid timestamp fields are `modified', `changed', `accessed', and `created'.
--time-style=STYLE How to format timestamps.  Valid timestamp styles are `default', `iso', `long-iso', and `full-iso'.
-u, --accessed Use the accessed timestamp field.
-U, --created Use the created timestamp field.
--no-permissions Suppress the permissions field.
--no-filesize Suppress the file size field.
--no-user Suppress the user field.
--no-time Suppress the time field.
-@, --extended List each file’s extended attributes and sizes.
--git [if exa was built with git support] List each file’s Git status, if tracked.
This adds a two-character column indicating the staged and unstaged statuses respectively.  The status character can be `-' for not modified, `M' for a modified file, `N' for a new file, `D' for deleted, `R' for renamed, `T' for type-change, `I' for ignored, and `U' for conflicted.
Directories will be shown to have the status of their contents, which is how `deleted' is possible: if a directory contains a file that has a certain status, it will be shown to have that status.
exa responds to the following environment variables:
COLUMNS Overrides the width of the terminal, in characters.
For example, `COLUMNS=80 exa' will show a grid view with a maximum width of 80 characters.
This option won’t do anything when exa’s output doesn’t wrap, such as when using the --long view.
EXA_STRICT Enables strict mode, which will make exa error when two command-line options are incompatible.
Usually, options can override each other going right-to-left on the command line, so that exa can be given aliases: creating an alias `exa=exa --sort=ext' then running `exa --sort=size' with that alias will run `exa --sort=ext --sort=size', and the sorting specified by the user will override the sorting specified by the alias.
In strict mode, the two options will not co-operate, and exa will error.
This option is intended for use with automated scripts and other situations where you want to be certain you’re typing in the right command.
EXA_GRID_ROWS Limits the grid-details view (`exa --grid --long') so it’s only activated when at least the given number of rows of output would be generated.
With widescreen displays, it’s possible for the grid to look very wide and sparse, on just one or two lines with none of the columns lining up. By specifying a minimum number of rows, you can only use the view if it’s going to be worth using.
EXA_ICON_SPACING Specifies the number of spaces to print between an icon (see the `--icons' option) and its file name.
Different terminals display icons differently, as they usually take up more than one character width on screen, so there’s no “standard” number of spaces that exa can use to separate an icon from text.  One space may place the icon too close to the text, and two spaces may place it too far away.  So the choice is left up to the user to configure depending on their terminal emulator.
LS_COLORS, EXA_COLORS Specifies the colour scheme used to highlight files based on their name and kind, as well as highlighting metadata and parts of the UI.
For more information on the format of these environment variables, see the exa_colors(5) manual page.
0      If everything goes OK.
1      If there was an I/O error during operation.
3      If there was a problem with the command-line arguments.
exa is maintained by Benjamin `ogham' Sago and many other contributors.
Website: https://the.exa.website/ Source code: https://github.com/ogham/exa Contributors: https://github.com/ogham/exa/graphs/contributors
• exa_colors(5)
MACCHANGER(1)                General Commands Manual               MACCHANGER(1)
macchanger - MAC Changer
macchanger [options] device
macchanger is a GNU/Linux utility for viewing/manipulating the MAC address for network interfaces.
macchanger accepts the following options:
-s, --show Prints the current MAC. This is the default action when no other option is specified.
-e, --ending Don't change the vendor bytes.
-a, --another Set random vendor MAC of the same kind.
-A     Set random vendor MAC of any kind.
-r, --random Set fully random MAC.
-p, --permanent Reset MAC address to its original, permanent hardware value.
-l, --list[=keyword] Print known vendors (with keyword in the vendor's description string).
-b, --bia When setting fully random MAC pretend to be a burned-in-address. If not used, the MAC will have the locally-administered bit set.
-m, --mac XX:XX:XX:XX:XX:XX, --mac=XX:XX:XX:XX:XX:XX Set the MAC XX:XX:XX:XX:XX:XX.
macchanger -A eth1
ifconfig (8)
Alvaro Lopez Ortega <alvaro@alobbs.com>.
FLATPAK(1)                           flatpak                          FLATPAK(1)
flatpak - Build, install and run applications and runtimes
flatpak [OPTION...] {COMMAND}
Flatpak is a tool for managing applications and the runtimes they use. In the Flatpak model, applications can be built and distributed independently from the host system they are used on, and they are isolated from the host system ('sandboxed') to some degree, at runtime.
Flatpak can operate in system-wide or per-user mode. The system-wide data (runtimes, applications and configuration) is located in $prefix/var/lib/flatpak/, and the per-user data is in $HOME/.local/share/flatpak/. Below these locations, there is a local repository in the repo/ subdirectory and installed runtimes and applications are in the corresponding runtime/ and app/ subdirectories.
System-wide remotes can be statically preconfigured by dropping flatpakrepo files into /etc/flatpak/remotes.d/.
In addition to the system-wide installation in $prefix/var/lib/flatpak/, which is always considered the default one unless overridden, more system-wide installations can be defined via configuration files in /etc/flatpak/installations.d/, which must define at least the id of the installation and the absolute path to it. Other optional parameters like DisplayName, Priority or StorageType are also supported.
Flatpak uses OSTree to distribute and deploy data. The repositories it uses are OSTree repositories and can be manipulated with the ostree utility. Installed runtimes and applications are OSTree checkouts.
Basic commands for building flatpaks such as build-init, build and build-finish are included in the flatpak utility. For higher-level build support, see the separate flatpak-builder(1) tool.
Flatpak supports installing from sideload repos. These are partial copies of a repository (generated by flatpak create-usb) that are used as installation source when offline (and online as a performance improvement). Such repositories are configured by creating symlinks to the sideload sources in the sideload-repos subdirectory of the installation directory (i.e. typically /var/lib/flatpak/sideload-repos). Additionally symlinks can be created in /run/flatpak/sideload-repos which is a better location for non-persistent sources (as it is cleared on reboot). These symlinks can point to either the directory given to flatpak create-usb which by default writes to the subpath .ostree/repo, or directly to an ostree repo.
The following global options are understood. Individual commands have their own options.
-v, --verbose Show debug information during command processing. Use -vv for more detail.
--ostree-verbose Show OSTree debug information during command processing.
--default-arch Print the default arch and exit.
--supported-arches Print the supported arches in priority order and exit.
--gl-drivers Print the list of active gl drivers and exit.
--installations Print paths of system installations and exit.
--print-system-only When the flatpak --print-updated-env command is run, only print the environment for system flatpak installations, not including the userâ€™s home installation.
--print-updated-env Print the set of environment variables needed to use flatpaks, amending the current set of environment variables. This is intended to be used in a systemd environment generator, and should not need to be run manually.
Commands for managing installed applications and runtimes:
flatpak-install(1) Install an application or a runtime from a remote or bundle.
flatpak-update(1) Update an installed application or runtime.
flatpak-uninstall(1) Uninstall an installed application or runtime.
flatpak-mask(1) Mask out updates and automatic installation.
flatpak-pin(1) Pin runtimes to prevent automatic removal.
flatpak-list(1) List installed applications and/or runtimes.
flatpak-info(1) Show information for an installed application or runtime.
flatpak-history(1) Show history.
flatpak-config(1) Manage flatpak configuration.
flatpak-repair(1) Repair flatpak installation.
flatpak-create-usb(1) Copy apps and/or runtimes onto removable media.
Commands for finding applications and runtimes:
flatpak-search(1) Search for applications and runtimes.
Commands for managing running applications:
flatpak-run(1) Run an application.
flatpak-kill(1) Stop a running application.
flatpak-override(1) Override permissions for an application.
flatpak-make-current(1) Specify the default version to run.
flatpak-enter(1) Enter the namespace of a running application.
Commands for managing file access:
flatpak-document-export(1) Grant an application access to a specific file.
flatpak-document-unexport(1) Revoke access to a specific file.
flatpak-document-info(1) Show information about a specific file.
flatpak-documents(1) List exported files.
Commands for managing the dynamic permission store:
flatpak-permission-remove(1) Remove item from permission store.
flatpak-permissions(1) List permissions.
flatpak-permission-show(1) Show app permissions.
flatpak-permission-reset(1) Reset app permissions.
flatpak-permission-set(1) Set app permissions.
Commands for managing remote repositories:
flatpak-remotes(1) List all configured remote repositories.
flatpak-remote-add(1) Add a new remote repository.
flatpak-remote-modify(1) Modify properties of a configured remote repository.
flatpak-remote-delete(1) Delete a configured remote repository.
flatpak-remote-ls(1) List contents of a configured remote repository.
flatpak-remote-info(1) Show information about a ref in a configured remote repository.
Commands for building applications:
flatpak-build-init(1) Initialize a build directory.
flatpak-build(1) Run a build command in a build directory.
flatpak-build-finish(1) Finalizes a build directory for export.
flatpak-build-export(1) Export a build directory to a repository.
flatpak-build-bundle(1) Create a bundle file from a ref in a local repository.
flatpak-build-import-bundle(1) Import a file bundle into a local repository.
flatpak-build-sign(1) Sign an application or runtime after its been exported.
flatpak-build-update-repo(1) Update the summary file in a repository.
flatpak-build-commit-from(1) Create a new commit based on an existing ref.
flatpak-repo(1) Print information about a repo.
Commands available inside the sandbox:
flatpak-spawn(1) Run a command in another sandbox.
File formats that are used by Flatpak commands:
flatpak-flatpakref(5) Reference to a remote for an application or runtime
flatpak-flatpakrepo(5) Reference to a remote
flatpak-remote(5) Configuration for a remote
flatpak-installation(5) Configuration for an installation location
flatpak-metadata(5) Information about an application or runtime
Besides standard environment variables such as XDG_DATA_DIRS and XDG_DATA_HOME, flatpak is consulting some of its own.
FLATPAK_USER_DIR The location of the per-user installation. If this is not set, $XDG_DATA_HOME/flatpak is used.
FLATPAK_SYSTEM_DIR The location of the default system-wide installation. If this is not set, /var/lib/flatpak is used (unless overridden at build time by --localstatedir or --with-system-install-dir).
FLATPAK_SYSTEM_CACHE_DIR The location where temporary child repositories will be created during pulls into the system-wide installation. If this is not set, a directory in /var/tmp/ is used. This is useful because it is more likely to be on the same filesystem as the system repository (thus increasing the chances for e.g. reflink copying), and we can avoid filling the user's home directory with temporary data.
FLATPAK_CONFIG_DIR The location of flatpak site configuration. If this is not set, /etc/flatpak is used (unless overridden at build time by --sysconfdir).
FLATPAK_RUN_DIR The location of flatpak runtime global files. If this is not set, /run/flatpak is used.
ostree(1), ostree.repo(5), flatpak-remote(5), flatpak-installation(5), https://www.flatpak.org
CHROOT(8)                         User Commands                        CHROOT(8)
chroot - run command or interactive shell with special root directory
chroot [OPTION] NEWROOT [COMMAND [ARG]...] chroot OPTION
Run COMMAND with root directory set to NEWROOT.
--groups=G_LIST specify supplementary groups as g1,g2,..,gN
--userspec=USER:GROUP specify user and group (ID or name) to use
--skip-chdir do not change working directory to '/'
If no command is given, run '"$SHELL" -i' (default: '/bin/sh -i').
Written by Roland McGrath.
chroot(2)
Full documentation <https://www.gnu.org/software/coreutils/chroot> or available locally via: info '(coreutils) chroot invocation'
MKTORRENT(1)                      User Commands                     MKTORRENT(1)
mktorrent - simple BitTorrent metainfo file creator
mktorrent [OPTIONS] <target directory or filename>
mktorrent is a command line utility to create BitTorrent metainfo files used by trackers and torrent clients. It can create metainfo files for single files or complete directories in a fast way.
-a, --announce=<url>[,<url>...] Specify the full announce URLs.  Additional -a adds backup trackers.
-c, --comment=<comment> Add a comment to the metainfo.
-d, --no-date Don't write the creation date.
-h, --help Show this help screen.
-l, --piece-length=<n> Set the piece length to 2^n bytes.  Default is 18, that is 2^18 = 256kB.
-n, --name=<name> Set the name of the torrent.  Default is the basename of the target.
-o, --output=<filename> Set the path and filename of the created file.  Default is <name>.torrent.
-p, --private Set the private flag.
-s, --source=<source> Add source string embedded in infohash.
-t, --threads=<n> Use <n> threads for calculating hashes.  Default is the number of CPU cores.
-w, --web-seed=<url>[,<url>...] Add web seed URLs.  Additional -w adds more URLs.
Written by Emil Renner Berthing <esmil@mailme.dk>.  As of May 2016 the upstream maintainer is Kai Nilsen <mktorrent@rudde.org>.
This manpage was written for the Debian mktorrent package by Paride Legovini <pl@ninthfloor.org> and Nico Golde <nion@debian.org>.
Please send bug reports, patches, feature requests, praise and general gossip about the program to: <mktorrent@rudde.org>.
This program is Free Software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.
More documentation at: <https://github.com/Rudde/mktorrent/wiki>.
RMDIR(1P)                   POSIX Programmer's Manual                  RMDIR(1P)
rmdir — remove directories
rmdir [-p] dir...
The rmdir utility shall remove the directory entry specified by each dir operand.
For each dir operand, the rmdir utility shall perform actions equivalent to the rmdir() function called with the dir operand as its only argument.
Directories shall be processed in the order specified. If a directory and a subdirectory of that directory are specified in a single invocation of the rmdir utility, the application shall specify the subdirectory before the parent directory so that the parent directory will be empty when the rmdir utility tries to remove it.
The rmdir utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-p        Remove all directories in a pathname. For each dir operand:
1. The directory entry it names shall be removed.
2. If the dir operand includes more than one pathname component, effects equivalent to the following command shall occur:
rmdir -p $(dirname dir)
dir       A pathname of an empty directory to be removed.
The following environment variables shall affect the execution of rmdir:
0    Each directory entry specified by a dir operand was removed successfully.
The definition of an empty directory is one that contains, at most, directory entries for dot and dot-dot.
If a directory a in the current directory is empty except it contains a directory b and a/b is empty except it contains a directory c:
rmdir -p a/b/c
removes all three directories.
On historical System V systems, the -p option also caused a message to be written to the standard output. The message indicated whether the whole path was removed or whether part of the path remained for some reason. The STDERR section requires this diagnostic when the entire path specified by a dir operand is not removed, but does not allow the status message reporting success to be written as a diagnostic.
The rmdir utility on System V also included a -s option that suppressed the informational message output by the -p option. This option has been omitted because the informational message is not specified by this volume of POSIX.1‐2017.
The System Interfaces volume of POSIX.1‐2017, remove(), rmdir(), unlink()
RAILS(1)                     General Commands Manual                    RAILS(1)
rails - Ruby on Rails deployment script
rails [options] destination(s)...
-d, --no-docs Deploys rails without any documentation.
-C, --copy Deploys rails by copying instead of linking vendor libraries.
-F, --force-overwrite Overwrites all previously deployed files, if any.
-D, --database Specify the database to be used. Supported values are mysql, oracle, postgresql, sqlite3, frontbase and ibm_db
-I, --internal Options to be passed to the upstream rails script.
Full documentation of rails are available after Ruby On Rails is deployed. For getting started instructions, see /usr/share/doc/rails/README.Debian
The upstream author of Ruby On Rails is David Heinemeier Hansson <david@loudthinking.com>. This manual page was written by Adam Majer <adamm@zombino.com>, for the Debian project (but may be used by others).
HELM(1)                      General Commands Manual                     HELM(1)
helm - a program to make music
helm [options] files... bar [options] files...
This manual page documents briefly the helm command.
helm is a program that makes sounds through synthesis
-v, --version Show version of program. Boooooooop beeeeeeep
rdfind(1)                            rdfind                            rdfind(1)
rdfind - finds duplicate files
rdfind [ options ] directory1 | file1 [ directory2 | file2 ] ...
rdfind finds duplicate files across and/or within several directories. It calculates checksum only if necessary.  rdfind runs in O(Nlog(N)) time with N being the number of files.
If two (or more) equal files are found, the program decides which of them is the original and the rest are considered duplicates. This is done by ranking the files to each other and deciding which has the highest rank. See section RANKING for details.
By default, no action is taken besides creating a file with the detected files and showing the possible amount of saved space.
If you need better control over the ranking than given, you can use some preprocessor which sorts the file names in desired order and then run the program using xargs. See examples below for how to use find and xargs in conjunction with rdfind.
To include files or directories that have names starting with -, use rdfind ./- to not confuse them with options.
Given two or more equal files, the one with the highest rank is selected to be the original and the rest are duplicates. The rules of ranking are given below, where the rules are executed from start until an original has been found. Given two files A and B which have equal size and content, the ranking is as follows:
If A was found while scanning an input argument earlier than B, A is higher ranked.
If A was found at a directory depth lower than B, A is higher ranked (A is closer to the root).
if A and B are found during scanning of the same input argument and share the same directory depth, the one that ranks highest depends on if deterministic operation is enabled. This is on by default, see option -deterministic). If enabled, which one ranks highest is unspecified but deterministic. If disabled, the one that was reported first from the file system is highest ranked.
Searching options etc:
-ignoreempty true|false Ignore empty files. Setting this to true (the default) is equivalent to -minsize 1, false is equivalent to -minsize 0.
-minsize N Ignores files with less than N bytes. Default is 1, meaning empty files are ignored.
-maxsize N Ignores files with N bytes or more. Default is 0, which means this check is disabled.
-followsymlinks true|false Follow symlinks. Default is false.
-removeidentinode true|false Removes items found which have identical inode and device ID. Default is true.
-checksum md5|sha1|sha256 What type of checksum to be used: md5, sha1 or sha256. The default is sha1 since version 1.4.0.
-deterministic true|false If set (the default), sort files of equal rank in an unspecified but deterministic order. This makes the behaviour independent of in which order files are listed when querying the file system.
-makesymlinks true|false Replace duplicate files with symbolic links. Default is false.
-makehardlinks true|false Replace duplicate files with hard links. Default is false.
-makeresultsfile true|false Make a results file in the current directory. Default is true. If the file exists, it is overwritten. This does not affect whether items are deleted. See -dryrun for how to disable deletions.
-outputname name Make the results file name to be "name" instead of the default results.txt.
-deleteduplicates true|false Delete (unlink) files. Default is false.
-sleep Xms Sleeps X milliseconds between reading each file, to reduce load. Default is 0 (no sleep). Note that only a few values are supported at present: 0,1-5,10,25,50,100 milliseconds.
-n, -dryrun true|false Displays what should have been done, don't actually delete or link anything. Default is false.
-h, -help, --help Displays a brief help message.
-v, -version, --version Displays the version number.
Search for duplicate files in the home directory and a backup directory: rdfind ~ /mnt/backup
Delete duplicates in a backup directory: rdfind -deleteduplicates true /mnt/backup
Search for duplicate files in directories called foo: find . -type d -name foo -print0 |xargs -0 rdfind
results.txt (the default name is results.txt and can be changed with option outputname, see above) The results file results.txt will contain one row per duplicate file found, along with a header row explaining the columns.  A text describes why the file is considered a duplicate:
DUPTYPE_UNKNOWN some internal error
DUPTYPE_FIRST_OCCURRENCE the file that is considered to be the original.
DUPTYPE_WITHIN_SAME_TREE files in the same tree (found when processing the directory in the same input argument as the original)
DUPTYPE_OUTSIDE_TREE the file is found during processing another input argument than the original.
0 on success, nonzero otherwise.
BUGS/FEATURES When specifying the same directory twice, it keeps the first encountered as the most important (original), and the rest as duplicates. This might not be what you want.
The symlink creates absolute links. This might not be what you want. To create relative links instead, you may use the symlink (2) command, which is able to convert absolute links to relative links.
Older versions unfortunately contained a misspelling on the word occurrence. This is now corrected (since 1.3), which might affect user scripts parsing the output file written by rdfind.
Avoid manipulating the directories while rdfind is reading.  rdfind is quite brittle in that case. Especially, when deleting or making links, rdfind can be subject to a symlink attack.  Use with care!
Paul Dreik 2006-2018, reachable at rdfind@pauldreik.se Rdfind can be found at https://rdfind.pauldreik.se/
Do you find rdfind useful? Drop me a line! It is always fun to hear from people who actually use it and what data collections they run it on.
Several persons have helped with suggestions and improvements: Niels MÃ¶ller, Carl Payne and Salvatore Ansani. Thanks also to you who tested the program and sent me feedback.
1.5.0 (release date 2021-08-13)
This program is distributed under GPLv2 or later, at your option.
md5sum(1), sha1sum(1), find(1), symlinks(2)
NOLOGIN(8)                    System Administration                   NOLOGIN(8)
nologin - politely refuse a login
nologin [-V] [-h]
nologin displays a message that an account is not available and exits non-zero. It is intended as a replacement shell field to deny login access to an account.
If the file /etc/nologin.txt exists, nologin displays its contents to the user instead of the default message.
The exit status returned by nologin is always 1.
-c, --command command
--init-file
-i --interactive
--init-file file
-i, --interactive
-l, --login
--noprofile
--norc
--posix
--rcfile file
-r, --restricted
These shell command-line options are ignored to avoid nologin error.
nologin is a per-account way to disable login (usually used for system accounts like http or ftp). nologin uses /etc/nologin.txt as an optional source for a non-default message, the login access is always refused independently of the file.
pam_nologin(8) PAM module usually prevents all non-root users from logging into the system. pam_nologin(8) functionality is controlled by /var/run/nologin or the /etc/nologin file.
The nologin command appeared in 4.4BSD.
login(1), passwd(5), pam_nologin(8)
The nologin 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/>.
CSVLOOK(1)                           csvkit                           CSVLOOK(1)
csvlook - csvlook Documentation
Renders a CSV to the command line in a Markdown-compatible, fixed-width format:
usage: csvlook [-h] [-d DELIMITER] [-t] [-q QUOTECHAR] [-u {0,1,2,3}] [-b] [-p ESCAPECHAR] [-z FIELD_SIZE_LIMIT] [-e ENCODING] [-L LOCALE] [-S] [--blanks] [--date-format DATE_FORMAT] [--datetime-format DATETIME_FORMAT] [-H] [-K SKIP_LINES] [-v] [-l] [--zero] [-V] [--max-rows MAX_ROWS] [--max-columns MAX_COLUMNS] [--max-column-width MAX_COLUMN_WIDTH] [-y SNIFF_LIMIT] [-I] [FILE]
Render a CSV file in the console as a Markdown-compatible, fixed-width table.
optional arguments: -h, --help            show this help message and exit --max-rows MAX_ROWS   The maximum number of rows to display before truncating the data. --max-columns MAX_COLUMNS The maximum number of columns to display before truncating the data. --max-column-width MAX_COLUMN_WIDTH Truncate all columns to at most this width. The remainder will be replaced with ellipsis. -y SNIFF_LIMIT, --snifflimit SNIFF_LIMIT Limit CSV dialect sniffing to the specified number of bytes. Specify "0" to disable sniffing entirely. -I, --no-inference    Disable type inference when parsing the input.
If a table is too wide to display properly try piping the output to less -S or truncating it using csvcut.
If the table is too long, try filtering it down with grep or piping the output to less.
Basic use:
csvlook examples/testfixed_converted.csv
This tool is especially useful as a final operation when piping through other tools:
csvcut -c 9,1 examples/realdata/FY09_EDU_Recipients_by_State.csv | csvlook
RUSTC(1)                          User Commands                         RUSTC(1)
rustc - The Rust compiler
rustc [OPTIONS] INPUT
This program is a compiler for the Rust language, available at https://www.rust-lang.org.
-h, --help Display the help message.
--cfg SPEC Configure the compilation environment.
-L [KIND=]PATH Add a directory to the library search path.  The optional KIND can be one of:
dependency only lookup transitive dependencies here
crate  only lookup local `extern crate` directives here
native only lookup native libraries here
framework only look for OSX frameworks here
all    look for anything here (the default)
-l [KIND=]NAME Link the generated crate(s) to the specified library NAME.  The optional KIND can be one of static, dylib, or framework.  If omitted, dylib is assumed.
--crate-type [bin|lib|rlib|dylib|cdylib|staticlib] Comma separated list of types of crates for the compiler to emit.
--crate-name NAME Specify the name of the crate being built.
--emit [asm|llvm-bc|llvm-ir|obj|link|dep-info|mir][=PATH] Configure the output that rustc will produce. Each emission may also have an optional explicit output PATH specified for that particular emission kind. This path takes precedence over the -o option.
--print [crate-name|file-names|sysroot|cfg|target-list|target-cpus| target-features|relocation-models|code-models|tls-models| target-spec-json|native-static-libs] Comma separated list of compiler information to print on stdout.
-g     Equivalent to -C debuginfo=2.
-O     Equivalent to -C opt-level=2.
-o FILENAME Write output to FILENAME. Ignored if multiple --emit outputs are specified which don't have an explicit path otherwise.
--out-dir DIR Write output to compiler‐chosen filename in DIR. Ignored if -o is specified.  Defaults to the current directory.
--explain OPT Provide a detailed explanation of an error message.
--test Build a test harness.
--target TARGET Target triple for which the code is compiled. This option defaults to the host’s target triple. The target triple has the general format <arch><sub>-<vendor>-<sys>-<abi>, where:
<arch> x86, arm, thumb, mips, etc.
<sub>  for example on ARM: v5, v6m, v7a, v7m, etc.
<vendor> pc, apple, nvidia, ibm, etc.
<sys>  none, linux, win32, darwin, cuda, etc.
<abi>  eabi, gnu, android, macho, elf, etc.
-W help Print 'lint' options and default settings.
-W OPT, --warn OPT Set lint warnings.
-A OPT, --allow OPT Set lint allowed.
-D OPT, --deny OPT Set lint denied.
-F OPT, --forbid OPT Set lint forbidden.
-C FLAG[=VAL], --codegen FLAG[=VAL] Set a codegen‐related flag to the value specified.  Use -C help to print available flags.  See CODEGEN OPTIONS below.
-V, --version Print version info and exit.
-v, --verbose Use verbose output.
--remap-path-prefix from=to Remap source path prefixes in all output, including compiler diagnostics, debug information, macro expansions, etc. The from=to parameter is scanned from right to left, so from may contain '=', but to may not.
This is useful for normalizing build products, for example by removing the current directory out of pathnames emitted into the object files. The replacement is purely textual, with no consideration of the current system's pathname syntax. For example --remap-path-prefix foo=bar will match foo/lib.rs but not ./foo/lib.rs.
--extern NAME=PATH Specify where an external rust library is located. These should match extern declarations in the crate's source code.
--sysroot PATH Override the system root.
-Z FLAG Set internal debugging options.  Use -Z help to print available options.
--color auto|always|never Configure coloring of output:
auto   colorize, if output goes to a tty (default);
always always colorize output;
never  never colorize output.
linker=/path/to/cc Path to the linker utility to use when linking libraries, executables, and objects.
link-args='-flag1 -flag2' A space‐separated list of extra arguments to pass to the linker when the linker is invoked.
lto    Perform LLVM link‐time optimizations.
target-cpu=help Selects a target processor.  If the value is 'help', then a list of available CPUs is printed.
target-feature='+feature1,-feature2' A comma‐separated list of features to enable or disable for the target.  A preceding '+' enables a feature while a preceding '-' disables it.  Available features can be discovered through llc -mcpu=help.
passes=val A space‐separated list of extra LLVM passes to run.  A value of 'list' will cause rustc to print all known passes and exit.  The passes specified are appended at the end of the normal pass manager.
llvm-args='-arg1 -arg2' A space‐separated list of arguments to pass through to LLVM.
save-temps If specified, the compiler will save more files (.bc, .o, .no-opt.bc) generated throughout compilation in the output directory.
rpath  If specified, then the rpath value for dynamic libraries will be set in either dynamic library or executable outputs.
no-prepopulate-passes Suppresses pre‐population of the LLVM pass manager that is run over the module.
no-vectorize-loops Suppresses running the loop vectorization LLVM pass, regardless of optimization level.
no-vectorize-slp Suppresses running the LLVM SLP vectorization pass, regardless of optimization level.
soft-float Generates software floating point library calls instead of hardware instructions.
prefer-dynamic Prefers dynamic linking to static linking.
no-integrated-as Force usage of an external assembler rather than LLVM's integrated one.
no-redzone Disable the use of the redzone.
relocation-model=[pic,static,dynamic-no-pic] The relocation model to use.  (Default: pic)
code-model=[small,kernel,medium,large] Choose the code model to use.
metadata=val Metadata to mangle symbol names with.
extra-filename=val Extra data to put in each output filename.
codegen-units=n Divide crate into n units to optimize in parallel.
remark=val Print remarks for these optimization passes (space separated, or "all").
no-stack-check Disable checks for stack exhaustion (a memory‐safety hazard!).
debuginfo=val Debug info emission level:
0      no debug info;
1      line‐tables only (for stacktraces and breakpoints);
2      full debug info with variable and type information.
opt-level=VAL Optimize with possible levels 0–3, s (optimize for size), or z (for minimal size)
Some of these affect only test harness programs (generated via rustc --test); others affect all programs which link to the Rust standard library.
RUST_TEST_THREADS The test framework Rust provides executes tests in parallel. This variable sets the maximum number of threads used for this purpose. This setting is overridden by the --test-threads option.
RUST_TEST_NOCAPTURE If set to a value other than "0", a synonym for the --nocapture flag.
RUST_MIN_STACK Sets the minimum stack size for new threads.
RUST_BACKTRACE If set to a value different than "0", produces a backtrace in the output of a program which panics.
To build an executable from a source file with a main function: $ rustc -o hello hello.rs
To build a library from a source file: $ rustc --crate-type=lib hello-lib.rs
To build either with a crate (.rs) file: $ rustc hello.rs
To build an executable with debug info: $ rustc -g -o hello hello.rs
rustdoc(1)
See https://github.com/rust-lang/rust/issues for issues.
See https://github.com/rust-lang/rust/graphs/contributors or use `git log --all --format='%cN <%cE>' | sort -u` in the rust source distribution.
This work is dual‐licensed under Apache 2.0 and MIT terms.  See COPYRIGHT file in the rust source distribution.
lxi(1)                       General Commands Manual                      lxi(1)
lxi - a tool for controlling LXI compatible instruments.
lxi [--help] [--version] <command> [<args>]
lxi is a commandline tool for controlling LXI compatible instruments such as modern oscilloscopes, power supplies, spectrum analyzers, etc.
-v, --version Display program version
discover [<options>] Search available networks for LXI devices
scpi [<options>] <SCPI-command> Send SCPI command
screenshot [<options>] [<filename>] Capture screenshot
benchmark [<options>] Benchmark
run [<options>] <filename> Run Lua script
-t, --timeout <seconds> Timeout in seconds
-m, --mdns Search via mDNS/DNS-SD
-a, --address <ip> IP address of LXI device
-p, --port Use port
-x, --hex Print response in hexadecimal
-i, --interactive Enter interactive mode
-s, --script <filename> Run script (plain text file with one SCPI command per line)
-r, --raw Use raw/TCP protocol
-p, --plugin <name> Use screenshot plugin by name
If this option is omitted the tool will automatically try to select the most suitable plugin.
-l, --list List available screenshot plugins
To write screenshot image to stdout simply use '-' as the output filename.
-c, --count <count> Number of request messages
Search for LXI instruments:
lxi discover
Search for LXI instruments using mDNS/DNS-SD:
lxi discover --mdns
Send SCPI command:
lxi scpi --address 10.0.0.42 "*IDN?"
Send SCPI command and dump response to file:
lxi scpi --address 10.0.0.42 "*IDN?" > response.txt
Capture screenshot from a Rigol 1000Z series oscilloscope:
lxi screenshot --address 10.0.0.42 --plugin rigol-1000z
Or by using screenshot plugin autodetection simply:
lxi screenshot --address 10.0.0.42
Note: Some LXI devices are slow to process SCPI commands, in which case you might need to take care to increase the timeout value.
Visit https://lxi-tools.github.io
Written by Martin Lund <martin.lund@keep-it-simple.com>
CSC(1)                     BSD General Commands Manual                    CSC(1)
csc — driver program for the CHICKEN Scheme compiler
csc [OPTION ...] [FILENAME ...]
csc is a program that invokes the CHICKEN compiler and the host systems C compiler to generate an executable from a Scheme source file or C files generated by CHICKEN.
FILENAME is a Scheme source file name with optional extension or a C/C++/Objective-C source, object or library file name with extension. OPTION may be one of the following:
-h, -help Display usage text and exit.
-v, -verbose Show compiler notes and tool-invocations.
-vv     Display information about translation progress.
-vvv    Display information about all compilation stages.
-version Display Scheme compiler version and exit.
-release Display release number and exit.
File and pathname options:
-o FILENAME, -output-file FILENAME Specifies target executable name.
-I PATHNAME, -include-path PATHNAME Specifies alternative path for included files.
-to-stdout Write compiler to stdout (implies -t).
-s, -shared, -dynamic Generate dynamically loadable shared object file.
Language options:
-D SYMBOL, -feature SYMBOL Register feature identifier.
-no-feature SYMBOL Disable builtin feature identifier.
-c++    Compile via a C++ source file (.cpp).
-objc   Compile via Objective-C source file (.m).
Syntax related options:
-i, -case-insensitive Don't preserve case of read symbols.
-K, -keyword-style STYLE Enable alternative keyword-syntax (prefix, suffix or none).
-no-parentheses-synonyms Disables list delimiter synonyms.
-no-symbol-escape Disables support for escaped symbols.
-r5rs-syntax Disables the CHICKEN extensions to R5RS syntax.
-compile-syntax Macros are made available at run-time.
-j MODULE, -emit-import-library MODULE Write compile-time module information into separate file.
-J, -emit-all-import-libraries Emit import-libraries for all defined modules.
-N, -no-module-registration Do not generate module registration code.
-no-compiler-syntax Disable expansion of compiler-macros.
-m NAME, -module NAME Wrap compiled code in module of the given name.
Translation options:
-x, -explicit-use Do not use units ‘library’ and ‘eval’ by default.
-P, -check-syntax Stop compilation after macro-expansion.
-A, -analyze-only Stop compilation after first analysis pass.
Debugging options:
-w, -no-warnings Disable warnings.
-d0, -d1, -d2, -d3, -debug-level NUMBER Set level of available debugging information.
-no-trace Disable rudimentary debugging information.
-profile Executable emits profiling information.
-accumulate-profile Executable emits profiling information in append mode.
-profile-name FILENAME Name of the generated profile information file.
-types FILENAME Load additional type database.
Optimization options:
-O, -O0, -O1, -O2, -O3, -O4, -O5, -optimize-level NUMBER Enable certain sets of optimization options.
-optimize-leaf-routines Enable leaf routine optimization.
-no-usual-integrations Standard procedures may be redefined.
-u, -unsafe Disable safety checks.
-local  Assume globals are only modified in current file.
-b, -block Enable block-compilation.
-disable-interrupts Disable interrupts in compiled code.
-f, -fixnum-arithmetic Assume all numbers are fixnums.
-disable-stack-overflow-checks Disables detection of stack-overflows.
-inline Enable inlining.
-inline-limit LIMIT Set inlining threshold.
-inline-global Enable cross-module inlining.
-specialize Perform type-based specialization of primitive calls.
-oi FILENAME, -emit-inline-file FILENAME Generate file with globally inlinable procedures (implies -inline -local).
-consult-inline-file FILENAME Explicitly load inline file.
-ot FILENAME, -emit-types-file FILENAME Write type-declaration information into file.
-no-argc-checks Disable argument count checks.
-no-bound-checks Disable bound variable checks.
-no-procedure-checks Disable procedure call checks.
-no-procedure-checks-for-usual-bindings Disable procedure call checks only for usual bindings.
-no-procedure-checks-for-toplevel-bindings Disable procedure call checks for toplevel bindings.
-strict-types Assume variable do not change their type.
-clustering Combine groups of local procedures into dispatch loop.
-lfa2   Perform additional lightweight flow-analysis pass.
Configuration options:
-unit NAME Compile file as a library unit.
-uses NAME Declare library unit as used.
-heap-size NUMBER Specifies heap-size of compiled executable.
-nursery NUMBER -stack-size NUMBER Specifies nursery size of compiled executable.
-X FILENAME, -extend FILENAME Load file before compilation commences.
-prelude EXPRESSION Add expression to beginning of source file.
-postlude EXPRESSION Add expression to end of source file.
-prologue FILENAME Include file before main source file.
-epilogue FILENAME Include file after main source file.
-e, -embedded Compile as embedded (don't generate ‘main()’).
-gui    Compile as GUI application.
-link NAME Link extension with compiled executable (implies ‘-uses’).
-R NAME, -require-extension NAME Require extension and import in compiled code.
-dll, -library Compile multiple units into a dynamic library.
-libdir DIRECTORY Override location of runtime library directory.
Options to other passes:
-C OPTION Pass option to C compiler.
-L OPTION Pass option to linker.
-I<DIR> Pass “-I<DIR>” to C compiler (add include path).
-L<DIR> Pass “-L<DIR>” to linker (add library path).
-k      Keep intermediate files.
-c      Stop after compilation to object files.
-t      Stop after translation to C.
-cc COMPILER Select a C compiler other than the default.
-cxx COMPILER Select a C++ compiler other than the default.
-ld COMPILER Select a linker other than the default.
-static-libs Link with static CHICKEN libraries and extensions.
-F<DIR> Pass “-F<DIR>” to C compiler (add framework header path on Mac OS X).
-framework NAME Passed to linker on Mac OS X.
-rpath PATHNAME Add directory to runtime library search path.
-Wl,... Pass linker options.
-strip  Strip resulting binary.
Inquiry options:
-home   Show home-directory (where support files go).
-cflags Show required C-compiler flags and exit.
-ldflags Show required linker flags and exit.
-libs   Show required libraries and exit.
-cc-name Show name of default C compiler used.
-cxx-name Show name of default C++ compiler used.
-ld-name Show name of default linker used.
-dry-run Just show commands executed, don't run them (implies ‘-v’).
Obscure options:
-debug MODES Display debugging output for the given modes.
-compiler PATHNAME Use a compiler other than the default ‘chicken’.
-raw    Do not generate implicit init- and exit code.
-emit-external-prototypes-first Emit prototypes for callbacks before foreign declarations.
-ignore-repository Do not refer to repository for extensions.
-keep-shadowed-macros Do not remove shadowed macros.
-host   Compile for host when configured for cross-compiling.
-private-repository Load extensions from executable path.
-deployed Link support file to be used from a deployed executable (sets ‘rpath’ accordingly, if supported on this platform.)
-no-elevation Embed manifest on Windows to supress elevation warnings for programs named ‘install’ or ‘setup’.
Options can be collapsed if unambiguous, so “-vkfO” is the same as “-v -k -fixnum-arithmetic -optimize”.
The following environment variables change the behaviour of csc:
CSC_OPTIONS  Can hold default options that should be passed to every invocation of csc.
The csc utility exits 0 on success, and >0 if an error occurs.
chicken(1)
More information can be found in the CHICKEN User's Manual: http://wiki.call-cc.org/manual/index
The CHICKEN Team
Submit bug reports by e-mail to chicken-janitors@nongnu.org
PINKY(1)                          User Commands                         PINKY(1)
pinky - lightweight finger
pinky [OPTION]... [USER]...
-l     produce long format output for the specified USERs
-b     omit the user's home directory and shell in long format
-h     omit the user's project file in long format
-p     omit the user's plan file in long format
-s     do short format output, this is the default
-f     omit the line of column headings in short format
-w     omit the user's full name in short format
-i     omit the user's full name and remote host in short format
-q     omit the user's full name, remote host and idle time in short format
A lightweight 'finger' program;  print user information.  The utmp file will be /var/run/utmp.
Written by Joseph Arceneaux, David MacKenzie, and Kaveh Ghazi.
Full documentation <https://www.gnu.org/software/coreutils/pinky> or available locally via: info '(coreutils) pinky invocation'