neulab/tldr huggingface dataset:
SDIFF(1)                          User Commands                         SDIFF(1)
sdiff - side-by-side merge of file differences
sdiff [OPTION]... FILE1 FILE2
Side-by-side merge of differences between FILE1 and FILE2.
-o, --output=FILE operate interactively, sending output to FILE
-i, --ignore-case consider upper- and lower-case to be the same
-E, --ignore-tab-expansion ignore changes due to tab expansion
-Z, --ignore-trailing-space ignore white space at line end
-b, --ignore-space-change ignore changes in the amount of white space
-W, --ignore-all-space ignore all white space
-B, --ignore-blank-lines ignore changes whose lines are all blank
-I, --ignore-matching-lines=RE ignore changes all whose lines match RE
--strip-trailing-cr strip trailing carriage return on input
-a, --text treat all files as text
-w, --width=NUM output at most NUM (default 130) print columns
-l, --left-column output only the left column of common lines
-s, --suppress-common-lines do not output common lines
-t, --expand-tabs expand tabs to spaces in output
--tabsize=NUM tab stops at every NUM (default 8) print columns
-d, --minimal try hard to find a smaller set of changes
-H, --speed-large-files assume large files, many scattered small changes
--diff-program=PROGRAM use PROGRAM to compare files
-v, --version output version information and exit
If a FILE is '-', read standard input.  Exit status is 0 if inputs are the same, 1 if different, 2 if trouble.
Written by Thomas Lord.
Report bugs to: bug-diffutils@gnu.org GNU diffutils home page: <https://www.gnu.org/software/diffutils/> General help using GNU software: <https://www.gnu.org/gethelp/>
cmp(1), diff(1), diff3(1)
The full documentation for sdiff is maintained as a Texinfo manual.  If the info and sdiff programs are properly installed at your site, the command
info sdiff
gh-api - Make an authenticated GitHub API request
gh api <endpoint> [flags]
Makes an authenticated HTTP request to the GitHub API and prints the response.
The endpoint argument should either be a path of a GitHub API v3 endpoint, or "graphql" to access the GitHub API v4.
Placeholder values "{owner}", "{repo}", and "{branch}" in the endpoint argument will get replaced with values from the repository of the current directory. Note that in some shells, for example PowerShell, you may need to enclose any value that contains "{...}" in quotes to prevent the shell from applying special meaning to curly braces.
The default HTTP request method is "GET" normally and "POST" if any parameters were added. Override the method with --method.
Pass one or more -f/--raw-field values in "key=value" format to add static string parameters to the request payload. To add non-string or otherwise dynamic values, see --field below. Note that adding request parameters will automatically switch the request method to POST. To send the parameters as a GET query string instead, use --method GET.
The -F/--field flag has magic type conversion based on the format of the value:
• literal values "true", "false", "null", and integer numbers get converted to appropriate JSON types;
• placeholder values "{owner}", "{repo}", and "{branch}" get populated with values from the repository of the current directory;
• if the value starts with "@", the rest of the value is interpreted as a filename to read the value from. Pass "-" to read from standard input.
For GraphQL requests, all fields other than "query" and "operationName" are interpreted as GraphQL variables.
Raw request body may be passed from the outside via a file specified by --input.  Pass "-" to read from standard input. In this mode, parameters specified via --field flags are serialized into URL query parameters.
In --paginate mode, all pages of results will sequentially be requested until there are no more pages of results. For GraphQL requests, this requires that the original query accepts an $endCursor: String variable and that it fetches the pageInfo{ hasNextPage, endCursor } set of fields from a collection.
--cache=0s      Cache the response, e.g. "3600s", "60m", "1h"
-F, --field=[]      Add a typed parameter in key=value format
-H, --header=[]      Add a HTTP request header in key:value format
--hostname=""      The GitHub hostname for the request (default "github.com")
-i, --include[=false]      Include HTTP response headers in the output
--input=""      The file to use as body for the HTTP request (use "-" to read from standard input)
-q, --jq=""      Query to select values from the response using jq syntax
-X, --method="GET"      The HTTP method for the request
--paginate[=false]      Make additional HTTP requests to fetch all pages of results
-p, --preview=[]      Opt into GitHub API previews
-f, --raw-field=[]      Add a string parameter in key=value format
--silent[=false]      Do not print the response body
-t, --template=""      Format the response using a Go template
# list releases in the current repository $ gh api repos/{owner}/{repo}/releases
# post an issue comment $ gh api repos/{owner}/{repo}/issues/123/comments -f body='Hi from CLI'
# add parameters to a GET request $ gh api -X GET search/issues -f q='repo:cli/cli is:open remote'
# set a custom HTTP header $ gh api -H 'Accept: application/vnd.github.v3.raw+json' ...
# opt into GitHub API previews $ gh api --preview baptiste,nebula ...
# print only specific fields from the response $ gh api repos/{owner}/{repo}/issues --jq '.[].title'
# use a template for the output $ gh api repos/{owner}/{repo}/issues --template \ '{{range .}}{{.title}} ({{.labels | pluck "name" | join ", " | color "yellow"}}){{"\n"}}{{end}}'
# list releases with GraphQL $ gh api graphql -F owner='{owner}' -F name='{repo}' -f query=' query($name: String!, $owner: String!) { repository(owner: $owner, name: $name) { releases(last: 3) { nodes { tagName } } } }
# list all repositories for a user $ gh api graphql --paginate -f query=' query($endCursor: String) { viewer { repositories(first: 100, after: $endCursor) { nodes { nameWithOwner } pageInfo { hasNextPage endCursor } } } }
QTCREATOR(1)                 General Commands Manual                QTCREATOR(1)
qtcreator - Integrated Development Environment for Qt
qtcreator [options] file(s)
Qt Creator is a lightweight, cross-platform integrated development environment (IDE) designed to make development with the Qt application framework faster and easier.
-help  Show summary of options.
-version Show version of program.
-client Attempt to connect to already running instance.
-noload <plugin> Do not load <plugin>
file(s) Files to load.
The full documentation is available in /usr/share/qtcreator/doc
This manual page was written by Adam Majer <adamm@zombino.com> and Jeremy Laine <jeremy.laine@m4x.org>, for the Debian project (and may be used by others).
XSEL(1)                      General Commands Manual                     XSEL(1)
xsel - manipulate the X selection.
xsel [OPTION]...
Retrieve and set the X selection.
The X server maintains three selections, called PRIMARY, SECONDARY and CLIPBOARD. The PRIMARY selection is conventionally used to implement copying and pasting via the middle mouse button. The SECONDARY and CLIPBOARD selections are less frequently used by application programs. This program operates on the PRIMARY selection unless otherwise specified.
By default, this program outputs the selection without modification if both standard input and standard output are terminals (ttys). Otherwise, the current selection is output if standard output is not a terminal (tty), and the selection is set from standard input if standard input is not a terminal (tty). If any input or output options are given then the program behaves only in the requested mode.
If both input and output is required then the previous selection is output before being replaced by the contents of standard input.
Input options
-a, --append append standard input to the selection. Implies -i.
-f, --follow append to selection as standard input grows. Implies -i.
-i, --input read standard input into the selection.
-o, --output write the selection to standard output.
Action options
-c, --clear clear the selection. Overrides all input options.
-d, --delete Request that the current selection be deleted. This not only clears the selection, but also requests to the program in which the selection resides that the selected contents be deleted. Overrides all input options.
Selection options
-p, --primary operate on the PRIMARY selection (default).
-s, --secondary operate on the SECONDARY selection.
-b, --clipboard operate on the CLIPBOARD selection.
-k, --keep Do not modify the selections, but make the PRIMARY and SECONDARY selections persist even after the programs they were selected in exit. (Conventionally, the CLIPBOARD selection is persisted by a separate special purpose program such as xclipboard(1)). Ignores all input and output options.
-x, --exchange exchange the PRIMARY and SECONDARY selections. Ignores all input and output options.
X options
-d displayname, --display displayname specify the server to use; see X(1).
-t ms, --selectionTimeout ms Specify the timeout in milliseconds within which the selection must be retrieved. A value of 0 (zero) specifies no timeout (default).
-l filename, --logfile filename Specify the file to log errors to when detached. (Default $HOME/.xsel.log)
-n, --nodetach Do not detach from the controlling terminal. Without this option, xsel will fork to become a background process in input, exchange and keep modes.
-h, --help display usage information and exit
-v, --verbose Print informative messages. Additional instances of -v raise the debugging level, ie. print more information.
There is no X selection buffer. The selection mechanism in X11 is an interclient communication mediated by the X server each time any program wishes to know the selection contents, eg. to perform a middle mouse button paste. In order to implement modification of the selection(s) (in input, keep and exchange modes) this program detaches from the terminal, spawning a child process to supply the new selection(s) on demand. This child exits immediately when any other program takes over the selection(s), eg. when the user next selects some text in a terminal window or by running xsel -c.
xsel conforms to the Inter-Client Communication Conventions Manual Version 2.0 (ICCCM2).
X(1), Xserver(1), xset(1), xclipboard(1), xpaste(1)
Conrad Parker <conrad@vergenet.net>, July 2001
7z(1)                        General Commands Manual                       7z(1)
7z - A file archiver with highest compression ratio
7z [adeltux] [-] [SWITCH] <ARCHIVE_NAME> <ARGUMENTS>...
7z uses plugins to handle archives.
-si    Read data from StdIn (eg: tar cf - directory | 7z a -si directory.tar.7z)
EXAMPLE 1 7z a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on archive.7z dir1 adds all files from directory "dir1" to archive archive.7z using "ultra settings"
EXAMPLE 2 7z a -sfx archive.exe dir1 add all files from directory "dir1" to SFX archive archive.exe (Remark : SFX archive MUST end with ".exe")
EXAMPLE 3 7z a -mhe=on -pmy_password archive.7z a_directory add all files from directory "a_directory" to the archive "archive.7z" (with data and header archive encryption on)
7za(1), 7zr(1), bzip2(1), gzip(1), lzip(1), zip(1)
INXI(8)                            inxi manual                           INXI(8)
inxi  - Command line system information script for console and IRC
inxi  - Single line, short form. Very basic output.
inxi [-AbCdDfFGhHiIlMnNopPrRsSu] [-c NUMBER] [-v NUMBER]
inxi [-t (c or m or cm or mc NUMBER)] [-x -OPTION(s)] [-xx -OPTION(s)] [-xxx -OPTION(s)]
inxi [--help] [--recommends] [--version] [-@ NUMBER]
inxi is a command line system information script built for for console and IRC. It is also used for forum technical support, as a debugging tool, to quickly ascertain user system configuration and hardware. inxi shows system hardware, CPU, drivers, Xorg, Desktop, Kernel, GCC version(s), Processes, RAM usage, and a wide variety of other useful information.
inxi output varies between CLI and IRC, with some default filters and color options applied to IRC use. Script colors can be turned off if desired with -c 0, or changed using the -c color options listed in the OPTIONS section below.
To trigger inxi output in your IRC client, pick the appropriate method from the list below:
Xchat, irssi (and many other IRC clients) /exec -o inxi [options]
If you leave off the -o, only you will see the output on your local IRC client.
Konversation /cmd inxi [options]
To run inxi in konversation as a native script if your distribution or inxi package did not do this for you, create this symbolic link:
ln -s /usr/local/bin/inxi /usr/share/kde4/apps/konversation/scripts/inxi
If inxi is somewhere else, change the path /usr/local/bin to wherever it is located.
Then you can start inxi directly, like this:
/inxi [options]
weechat /shell -o inxi [options]
For Weechat to run external scripts like inxi, you have to install shell.py (if you don't already have it).  To install shell.py, run this command inside of weechat:
/weeget install shell.py
Then to run inxi, you would enter a command like this:
/shell -o inxi -bx
If you leave off the -o, only you will see the output on your local weechat.
In order to maintain basic privacy and security, inxi filters out automatically on IRC things like your network card mac address, WAN and LAN IP, your /home username directory in partitions, and a few other things.
Because inxi is often used on forums for support, you can also trigger this filtering with the -z option (-Fz, for example). To override the IRC filter, you can use the -Z option. This can be useful to debug network connection issues online in a private chat, for example.
Options can be combined if they do not conflict. Either group the letters together or separate them.
Letters with numbers can have no gap or a gap at your discretion unless using  -t.
For example: inxi -AG or inxi -A -G or inxi -c10
-A     Show Audio/sound card information.
-b     Shows basic output, short form (previously -d). Same as: inxi -v 2
-c [0-32] Available color schemes. Scheme number is required.
Supported color schemes: 0-32
-c [94-99] Color selectors run a color selector option  prior to inxi starting which lets you set the config file value for the selection.
Color selectors for each type display
(NOTE: irc and global only show safe color set):
-c 94  - Console, out of X
-c 95  - Terminal, running in X - like xTerm
-c 96  - Gui IRC, running in X - like Xchat, Quassel, Konversation etc.
-c 97  - Console IRC running in X - like irssi in xTerm
-c 98  - Console IRC not in  X
-c 99  - Global - Overrides/removes all settings.
Setting specific color type removes the global color selection.
-C     Show full CPU output, including per CPU clockspeed.
-d     Shows optical drive data. Same as -Dd. With -x, adds features line to output.  -xx adds a few more features.
-D     Show full hard Disk info, not only model, ie: /dev/sda ST380817AS 80.0GB.
-f     Show all cpu flags used, not just the short list. Not shown with -F to avoid spamming.
-F     Show Full output for inxi. Includes all Upper Case line letters, plus -s and -n.  Does not show extra verbose options like -x -d -f -u -l -o -p -t -r unless you use that argument.
-G     Show Graphic card information (card, x type, resolution, glx renderer, version).
-h     This help menu.
--help Same as -h
-H     This help menu, plus developer options. Do not use dev options in normal operation!
-i     Show Wan IP address, and shows local interfaces (requires ifconfig network tool).  Same as -Nni. Not shown with -F for user security reasons, you shouldn't paste your local/wan IP.
-I     Show Information: processes, uptime, memory, irc client, inxi version.
-l     Show partition labels. Default: short partition -P. For full -p output, use: -pl (or -plu).
-M     Show machine data. Motherboard, Bios, and if present, System Builder (Like Lenovo).  Older systems/kernels without the required /sys data can use dmidecode instead, run as root.
-n     Show Advanced Network card information. Same as -Nn. Shows interface, speed, mac id, state, etc.
-N     Show Network card information. With -x, shows PCI BusID, Port number.
-o     Show unmounted partition information (includes UUID and LABEL if available).  Shows file system type if you have file installed, if you are root OR if you have added to /etc/sudoers (sudo v. 1.7 or newer):
<username> ALL = NOPASSWD: /usr/bin/file (sample)
-p     Show full partition information (-P plus all other detected partitions).
-P     Show Partition information (shows what -v 4 would show, but without extra data).  Shows, if detected: / /boot /home /tmp /usr /var. Use -p to see all mounted partitions.
-r     Show distro repository data. Currently supported repo types: APT (Debian, Ubuntu + derived versions)
PACMAN (Arch Linux + derived versions)
PISI (Pardus + derived versions)
YUM. (Fedora, Redhat, maybe Suse + derived versions)
(as distro data is collected more will be added. If your's is missing please show us how to get this information and we'll try to add it.)
-R     Show RAID data. Shows RAID devices, states, levels, and components, and extra data with -x / -xx.  If device is resyncing, shows resync progress line as well.
--recommends Checks inxi application dependencies + recommends, and directories, then shows what package(s) you need to install to add support for that feature.
-s     Show sensors output (if sensors installed/configured): mobo/cpu/gpu temp; detected fan speeds. Gpu temp only for Fglrx/Nvidia drivers. Nvidia shows screen number for > 1 screens.
-S     Show System information: host name, kernel, desktop environment (if in X), distro. With -xx show dm - or startx - (only shows if present and running if out of X), and if in X, with -xxx show more desktop info, like shell/panel etc.
-t [c or m or cm or mc NUMBER] Show processes. If followed by numbers 1-20, shows that number of processes for each type (default: 5; if in irc, max: 5)
Make sure to have no space between letters and numbers (-t cm10 - right, -t cm 10 - wrong).
-t c   - cpu only. With -x, shows also memory for that process on same line.
-t m   - memory only. With -x, shows also cpu for that process on same line.
-t cm  - cpu+memory. With -x, shows also cpu or memory for that process on same line.
-u     Show partition UUIDs. Default: short partition -P. For full -p output, use: -pu (or -plu).
-U     Auto-update script. Note: if you installed as root, you must be root to update, otherwise user is fine. Also installs /updates this Man Page to: -/usr/share/man/man8 This requires that you be root to write to that directory.
-V     inxi version information. Prints information then exits.
--version same as -V
-v     Script verbosity levels. Verbosity level number is required. Should not be used with -b or -F.
Supported levels: 0-7 Examples : inxi -v 4  or  inxi -v4
-v 0   - Short output, same as: inxi
-v 1   - Basic verbose, -S + basic CPU + -G + basic Disk + -I.
-v 2   - Adds networking card (-N), Machine (-M) data, and shows basic hard disk data (names only). Same as: inxi -b
-v 3   - Adds advanced CPU (-C); network (-n) data; triggers -x advanced data option.
-v 4   - Adds partition size/filled data (-P) for (if present):/, /home, /var/, /boot Shows full disk data (-D)
-v 5   - Adds audio card (-A); sensors (-s), partition label (-l) and UUID (-u), short form of optical drives.
-v 6   - Adds full partition data (-p), unmounted partition data (-o), optical drive data (-d); triggers -xx extra data option.
-v 7   - Adds network IP data (-i); triggers -xxx.
-z     Adds security filters for IP addresses, Mac, and user home directory name. Default on for irc clients.
-Z     Absolute override for output filters. Useful for debugging networking issues in irc for example.
These options are for long form only, and can be triggered by one or more -x, like -xx.  Alternately, the -v options trigger them in the following way: -v 3 adds -x; -v 6 adds -xx; -v 7 adds -xxx
These extra data triggers can be useful for getting more in-depth data on various options.  Can be added to any long form option list, like: -bxx or -Sxxx
There are 3 extra data levels: -x; -xx; and -xxx
The following shows which lines / items get extra information with each extra data level.
-x -C  - bogomips on Cpu
-x -d  - Adds items to features line of optical drive; adds rev version to optical drive.
-x -D  - Hdd temp with disk data if you have hddtemp installed, if you are root OR if you have added to /etc/sudoers (sudo v. 1.7 or newer):
<username> ALL = NOPASSWD: /usr/sbin/hddtemp (sample)
-x -G  - Direct rendering status for Graphics (in X).
-x -G  - (for single gpu, nvidia driver) screen number gpu is running on.
-x -i  - Show IPv6 as well for LAN interface (IF) devices.
-x -I  - Show system GCC, default. With -xx, also show other installed GCC versions.
-x -N -A - Adds version/port(s)/driver version (if available) for Network/Audio;
-x -N -A -G - Network, audio, graphics, shows PCI Bus ID/Usb ID number of card
-x -R  - Shows component raid id. Adds second RAID Info line: raid level; report on drives (like 5/5); blocks; chunk size; bitmap (if present). Resync line, shows blocks synced/total blocks.
-x -S  - Desktop toolkit if avaliable (GNOME/XFCE/KDE only); Kernel gcc version
-x -t  - Adds memory use output to cpu (-xt c), and cpu use to memory (-xt m).
-xx -D - Adds disk serial number
-xx -I - Adds other detected installed gcc versions to primary gcc output (if present).
-xx -M - Adds chassis information, if any data for that is available.
-xx -R - Adds superblock (if present); algorythm, U data. Adds system info line (kernel support, read ahead, raid events). Adds if present, unused device line.  If device is resyncing, shows resync progress line as well
-xx -S - Adds, if run in X, display manager type to Desktop information, if present. If none, shows N/A.  Supports most known display managers, like xdm, gdm, kdm, slim, lightdm, or mdm.
-xx -@ <11-14> - Automatically uploads debugger data tar.gz file to ftp.techpatterns.com.
-xxx -S - Adds, if run in X, shell/panel type info to Desktop information, if present. If none, shows nothing.  Supports some current desktop extras like gnome-panel, lxde-panel, and others. Added mainly for Mint support.
-%     Overrides defective or corrupted data.
-@     Triggers debugger output. Requires debugging level 1-14 (8-10 - logging of data).  Less than 8 just triggers inxi debugger output on screen.
-@ [1-7] - On screen debugger output
-@ 8   - Basic logging. Check  /home/yourname/.inxi/inxi*.log
-@ 9   - Full file/sys info logging
-@ 10  - Color logging.
-@ <11-14> The following create a tar.gz file of system data, plus collecting the inxi output to file: To automatically upload debugger data tar.gz file to ftp.techpatterns.com: inxi -xx@ <11-14> For alternate ftp upload locations: Example:
inxi -! ftp.yourserver.com/incoming -xx@ 14
-@ 11  - With data file of xiin read of /sys
-@ 12  - With xorg conf and log data, xrandr, xprop, xdpyinfo, glxinfo etc.
-@ 13  - With data from dev, disks, partitions, etc., plus xiin data file.
-@ 14  - Everything, full data collection
BitchX, Gaim/Pidgin, ircII, Irssi, Konversation, Kopete, KSirc, KVIrc, Weechat, and Xchat. Plus any others that are capable of displaying either built in or external script output.
inxi will read the following configuration/initialization files in the following order:
/etc/inxi.conf
$HOME/.inxi/inxi.conf
See wiki pages for more information on how to set these up:
http://code.google.com/p/inxi/wiki/script_configuration_files
Please report bugs using the following resources.
You may be asked to run the inxi debugger tool which will upload a data dump of all system files for use in debugging inxi. These data dumps are very important since they provide us with all the real system data inxi uses to parse out its report.
inxi wiki, file an issue report: http://code.google.com/p/inxi/issues/list
post on inxi developer forums: http://techpatterns.com/forums/forum-32.html
You can also visit irc.oftc.net channel: #smxi to post issues.
http://code.google.com/p/inxi
inxi is is a fork of locsmif's largely unmaintained yet very clever, infobash script.
Original infobash author and copyright holder: Copyright (C) 2005-2007 Michiel de Boer a.k.a. locsmif
inxi version: Copyright (C) 2008-12 Scott Rogers & Harald Hope
Further fixes (listed as known): Horst Tritremmel <hjt at sidux.com>
Steven Barrett (aka: damentz) - usb audio patch; swap percent used patch
And a special thanks to the nice people at irc.oftc.net channels #linux- smokers-club and #smxi, who  all really have to be considered to be co- developers because of their non-stop enthusiasm and willingness to provide real time testing and debugging of inxi development.
Without a wide range of diverse Linux kernel based Free Desktop systems to test on, we could never have gotten inxi to be as reliable and solid as it's turning out to be.
And of course, big thanks locsmif, who figured out a lot of the core methods, logic, and tricks used in inxi.
Further thanks to the various inxi package maintainers, distro support people, forum moderators, and others, who contribute ideas, suggestions, and patches.
This Man page was created by aus9, with help from Harald (aka h2).
JPEGOPTIM(1)                 General Commands Manual                JPEGOPTIM(1)
jpegoptim - utility to optimize/compress JPEG/JFIF files.
jpegoptim [ options ] [ filenames ]
jpegoptim is used to optimize/compress jpeg files. Program supports lossless optimization, which is based on optimizing the Huffman tables. And so called "lossy" optimization where in addition to optimizing Huffman tables user can specify upperlimit for image quality.
NOTE! By default jpegoptim modifies the input files (if they are optimized), to preserve original files use option -d to specify alternate directory for saving the optimized files to.
Only normal files are optimized (symbolic links and special files are skipped).  Also, any other hard links to the file being optimized (as created using link(2)) are unaffected.
Options may be either the traditional POSIX one letter options, or the GNU style long options.  POSIX style options start with a single ``-'', while GNU long options start with ``--''.
Options offered by jpegoptim are the following:
-d<path>, --dest=<path> Sets alternative destination directory where to save optimized files (default is to overwrite the originals). Please note that unchanged files won't be added to the destination directory. This means if the source file can't be compressed, no file will be created in the destination path.
-f, --force Force optimization, even if the result would be larger than the original file.
-h, --help Displays short usage information and exits.
-m<quality>, --max=<quality> Sets the maximum image quality factor (disables lossless optimization mode, which is by default enabled). This option will reduce quality of those source files that were saved using higher quality setting.  While files that already have lower quality setting will be compressed using the lossless optimization method.
Valid values for quality parameter are: 0 - 100
-n, --noaction Don't really optimize files, just print results.
-S<size>, --size=<size> Try to optimize file to given size (disables lossless optimization mode). Target size is specified either in kilobytes (1 - n) or as percentage (1% - 99%) of the original file size.
-T<threshold>, --threshold=<threshold> Keep the file unchanged if the compression gain is lower than the threshold (%).
Valid values for threshold are: 0 - 100
-b, --csv Print progress info in CSV format.
-o, --overwrite Overwrite target file even if it exists (when using -d option).
-p, --preserve Preserve file modification times.
-P, --preserve-perms Preserve file permissions (owner/group) by overwriting the original file. This is slightly less safe than the default mode of operation (where new file is first saved as temporary file and then renamed over the original file).  In this mode a backup of the original file is made with .jpegoptim.bak extension, and this file is removed after the original file has been successfully replaced. NOTE! if running jpegoptim as root there is generally no need to use this option, as jpegoptim is able to preserve file permissions when run by root in default mode.
-q, --quiet Quiet mode.
-t, --totals Print totals after processing all files.
-v, --verbose Enables verbose mode (positively chatty).
--all-normal Force all output files to be non-progressive. Can be used to convert all input files to progressive JPEGs when used with --force option.
--all-progressive Force all output files to be progressive. Can be used to convert all normal (non-progressive) JPEGs input files to progressive when used with --force option.
-s, --strip-all Strip all markers from output file. (NOTE! by default only Comment & Exif/IPTC/PhotoShop/ICC/XMP markers are kept, everything else is discarded).  Output JPEG still likely will contains one or two markers (JFIF and Adobe APP14) depending on colorspace used in the image, as these markers are generated by the libjpeg encoder automatically.
--strip-none Preserve "all" markers in the image. This will leave all markers untouched in the image, except JFIF (APP0) and Adobe (APP14) markers as those get regenerated by the libjpeg library.
--strip-com Strip Comment (COM) markers from output file.
--strip-exif Strip EXIF markers from output file.
--strip-iptc Strip IPTC / Adobe Photoshop (APP13) markers from output file.
--strip-icc Strip ICC profiles from output file.
--strip-xmp Strip XMP profiles from output file.
--stdout Send output image to standard output. Note, if optimization didn't create smaller file than the input file, then no output (image) is sent to standard output. (Option -f can be used to force output of image always, even if optimized image was not smaller than input).
--stdin Read input image from standard input. When this option is used then only one image is read from standard output. Any (other) input files specified on command line are ignored.  Note, if input file '-' is seen on command line then standard input is also assumed.
Currently this option will explicitly enable -f option, thus output image is always sent to standard output (even if no optimization was possible).
When using --size option, resulting file is not always exactly the requested size. Workaround is to re-run jpegoptim on the same file again which often will result file closer to target size.
jpeginfo(1)
Timo Kokkonen <tjko@iki.fi>
Copyright (C) 1996-2018  Timo Kokkonen
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 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
GIST(1)                            Gist manual                           GIST(1)
gist - upload code to https://gist.github.com
Synopsis The gist gem provides a gist command that you can use from your terminal to upload content to https://gist.github.com/.
Installation •   If you have ruby installed:
gem install gist
•   If you´re using Bundler:
source :rubygems gem ´gist´
•   For OS X, gist lives in Homebrew
brew install gist
•   For FreeBSD, gist lives in ports
pkg install gist
Command •   To upload the contents of a.rb just:
gist a.rb
•   Upload multiple files:
gist a b c gist *.rb
•   By default it reads from STDIN, and you can set a filename with -f.
gist -f test.rb <a.rb
•   Alternatively, you can just paste from the clipboard:
gist -P
•   Use -p to make the gist private:
gist -p a.rb
•   Use -d to add a description:
gist -d "Random rbx bug" a.rb
•   You can update existing gists with -u:
gist -u GIST_ID FILE_NAME gist -u 42f2c239d2eb57299408 test.txt
•   If you´d like to copy the resulting URL to your clipboard, use -c.
gist -c <a.rb
•   If you´d like to copy the resulting embeddable URL to your clipboard, use -e.
gist -e <a.rb
•   And you can just ask gist to open a browser window directly with -o.
gist -o <a.rb
•   To list (public gists or all gists for authed user) gists for user
gist -l : all gists for authed user gist -l defunkt : list defunkt´s public gists
To read a gist and print it to STDOUT
gist -r GIST_ID gist -r 374130
•   See gist --help for more detail.
Login Before you use gist for the first time you will need to log in. There are two supported login flows:
1.  The Github device-code Oauth flow. This is the default for authenticating to github.com, and can be enabled for Github Enterprise by creating an Oauth app, and exporting the environment variable GIST_CLIENT_ID with the client id of the Oauth app.
2.  The (deprecated) username and password token exchange flow. This is the default for GitHub Enterprise, and can be used to log into github.com by exporting the environment variable GIST_USE_USERNAME_AND_PASSWORD.
The device-code flow This flow allows you to obtain a token by logging into GitHub in the browser and typing a verification code. This is the preferred mechanism.
gist --login Requesting login parameters... Please sign in at https://github.com/login/device and enter code: XXXX-XXXX Success! https://github.com/settings/connections/applications/4f7ec0d4eab38e74384e
The returned access_token is stored in ~/.gist and used for all future gisting. If you need to you can revoke access from https://github.com/settings/connections/applications/4f7ec0d4eab38e74384e.
The username-password flow This flow asks for your GitHub username and password (and 2FA code), and exchanges them for a token with the "gist" permission (your username and password are not stored). This mechanism is deprecated by GitHub, but may still work with GitHub Enterprise.
gist --login Obtaining OAuth2 access_token from GitHub. GitHub username: ConradIrwin GitHub password: 2-factor auth code: Success! https://github.com/settings/tokens
This token is stored in ~/.gist and used for all future gisting. If you need to you can revoke it from https://github.com/settings/tokens, or just delete the file.
If you have a complicated authorization requirement you can manually create a token file by pasting a GitHub token with gist scope (and maybe the user:email for GitHub Enterprise) into a file called ~/.gist. You can create one from https://github.com/settings/tokens
This file should contain only the token (~40 hex characters), and to make it easier to edit, can optionally have a final newline (\n or \r\n).
For example, one way to create this file would be to run:
(umask 0077 && echo MY_SECRET_TOKEN > ~/.gist)
The umask ensures that the file is only accessible from your user account.
GitHub Enterprise If you´d like gist to use your locally installed GitHub Enterprise https://enterprise.github.com/, you need to export the GITHUB_URL environment variable (usually done in your ~/.bashrc).
export GITHUB_URL=http://github.internal.example.com/
Once you´ve done this and restarted your terminal (or run source ~/.bashrc), gist will automatically use GitHub Enterprise instead of the public github.com
Your token for GitHub Enterprise will be stored in .gist.<protocol>.<server.name>[.<port>] (e.g. ~/.gist.http.github.internal.example.com for the GITHUB_URL example above) instead of ~/.gist.
If you have multiple servers or use Enterprise and public GitHub often, you can work around this by creating scripts that set the env var and then run gist. Keep in mind that to use the public GitHub you must unset the env var. Just setting it to the public URL will not work. Use unset GITHUB_URL
Token file format If you cannot use passwords, as most Enterprise installations do, you can generate the token via the web interface and then simply save the string in the correct file. Avoid line breaks or you might see: $ gist -l Error: Bad credentials
You can also use Gist as a library from inside your ruby code:
Gist.gist("Look.at(:my => ´awesome´).code")
If you need more advanced features you can also pass:
•   :access_token to authenticate using OAuth2 (default is `File.read("~/.gist")).
•   :filename to change the syntax highlighting (default is a.rb).
•   :public if you want your gist to have a guessable url.
•   :description to add a description to your gist.
•   :update to update an existing gist (can be a URL or an id).
•   :copy to copy the resulting URL to the clipboard (default is false).
•   :open to open the resulting URL in a browser (default is false).
NOTE: The access_token must have the gist scope and may also require the user:email scope.
•   If you want to upload multiple files in the same gist, you can:
Gist.multi_gist("a.rb" => "Foo.bar", "a.py" => "Foo.bar")
•   If you´d rather use gist´s builtin access_token, then you can force the user to obtain one by calling:
Gist.login!
•   This will take them through the process of obtaining an OAuth2 token, and storing it in ~/.gist, where it can later be read by Gist.gist
Configuration •   If you´d like -o or -c to be the default when you use the gist executable, add an alias to your ~/.bashrc (or equivalent). For example:
alias gist=´gist -c´
•   If you´d prefer gist to open a different browser, then you can export the BROWSER environment variable:
export BROWSER=google-chrome
If clipboard or browser integration don´t work on your platform, please file a bug or (more ideally) a pull request.
If you need to use an HTTP proxy to access the internet, export the HTTP_PROXY or http_proxy environment variable and gist will use it.
Meta-fu Thanks to @defunkt and @indirect for writing and maintaining versions 1 through 3. Thanks to @rking and @ConradIrwin for maintaining version 4.
Licensed under the MIT license. Bug-reports, and pull requests are welcome.
ZEEK(8)                  System Administration Utilities                 ZEEK(8)
zeek - passive network traffic analyzer
zeek  [options] [file ...]
Zeek is primarily a security monitor that inspects all traffic on a link in depth for signs of suspicious activity. More generally, however, Zeek supports a wide range of traffic analysis tasks even outside of the security domain, including performance measurements and helping with trouble-shooting.
Zeek comes with built-in functionality for a range of analysis and detection tasks, including detecting malware by interfacing to external registries, reporting vulnerable versions of software seen on the network, identifying popular web applications, detecting SSH brute- forcing, validating SSL certificate chains, among others.
<file> policy file, or read stdin
-a, --parse-only exit immediately after parsing scripts
-b, --bare-mode don't load scripts from the base/ directory
-d, --debug-policy activate policy file debugging
-e, --exec <zeek code> augment loaded policies by given code
-f, --filter <filter> tcpdump filter
-h, --help|-? command line help
-i, --iface <interface> read from given interface
-p, --prefix <prefix> add given prefix to policy file resolution
-r, --readfile <readfile> read from given tcpdump file
-s, --rulefile <rulefile> read rules from given file
-t, --tracefile <tracefile> activate execution tracing
-w, --writefile <writefile> write to given tcpdump file
-v, --version print version and exit
-x, --print-state <file.bst> print contents of state file
-C, --no-checksums ignore checksums
-F, --force-dns force DNS
-I, --print-id <ID name> print out given ID
-N, --print-plugins print available plugins and exit (-NN for verbose)
-P, --prime-dns prime DNS
-Q, --time print execution time summary to stderr
-R, --replay <events.bst> replay events
-S, --debug-rules enable rule debugging
-T, --re-level <level> set 'RE_level' for rules
-U, --status-file <file> Record process status in file
-W, --watchdog activate watchdog timer
-X, --zeekygen <cfgfile> generate documentation based on config file
--pseudo-realtime[=<speedup>] enable pseudo-realtime for performance evaluation (default 1)
--load-seeds <file> load seeds from given file
--save-seeds <file> save seeds to given file
The following option is available only when Zeek is built with the --enable-debug configure option:
-B, --debug <dbgstreams> Enable debugging output for selected streams ('-B help' for help)
The following options are available only when Zeek is built with gperftools support (use the --enable-perftools and --enable-perftools-debug configure options):
-m, --mem-leaks show leaks
-M, --mem-profile record heap
ZEEKPATH file search path
ZEEK_PLUGIN_PATH plugin search path
ZEEK_PLUGIN_ACTIVATE plugins to always activate
ZEEK_PREFIXES prefix list
ZEEK_DNS_FAKE disable DNS lookups
ZEEK_SEED_FILE file to load seeds from
ZEEK_LOG_SUFFIX ASCII log file extension
ZEEK_PROFILER_FILE Output file for script execution statistics
ZEEK_DISABLE_ZEEKYGEN Disable Zeekygen (Broxygen) documentation support
zeek was written by The Zeek Project <info@zeek.org>.
RC-UPDATE(8)                 System Manager's Manual                RC-UPDATE(8)
rc-update â€” add and remove services to and from a runlevel
rc-update [-s, --stack] add service [runlevel ...] rc-update [-s, --stack] [-a, --all] delete service [runlevel ...] rc-update [-u, --update] [-v, --verbose] show [runlevel ...]
OpenRC uses named runlevels.  Rather than editing some obscure file or managing a directory of symlinks, rc-update exists to quickly add or delete services to and from from different runlevels.  All services must reside in the /etc/init.d or /usr/local/etc/init.d directories.  They must also be standard OpenRC scripts, meaning they must use openrc-run.
add service             Add the service to the runlevel or the current one if none given.  Services added to the boot runlevel must exist in /etc/init.d.
delete service          Delete the service from the runlevel or the current one if none given.
show                    Show all enabled services and the runlevels they belong to.  If you specify runlevels to show, then only those will be included in the output.
-v, --verbose           Show all services.
-u, --update            Forces an update of the dependency tree cache. This may be needed in the event of clock skew (a file in /etc is newer than the system clock).
If the -s, --stack option is given then we either add or remove the runlevel from the runlevel.  This allows inheritance of runlevels.
If the -a, --all option is given, we remove the service from all runlevels. This is useful, for example, to clean up the dangling symlinks after a service is removed.
openrc(8), openrc-run(8), rc-status(8)
Roy Marples <roy@marples.name> The OpenRC Team <openrc@gentoo.org>
PRT(1p)                User Contributed Perl Documentation               PRT(1p)
prt - Command line frontend of App::PRT
$ prt <command> <args> $ prt <command> <args> <files>
prt is the command line frontend of App::PRT.
•   replace_token
Replace "foo" token with "bar".
prt replace_token foo bar
Replace "foo" token with "bar" but target statements must have "bazz" token.
prt replace_token foo bar --in-statement bazz
•   rename_class
Rename "Foo" class to "Bar" class.
prt rename_class Foo Bar
•   rename_namespace
Rename "Foo" and "Foo::*" classes to "Bar" and "Bar::*" classes.
prt rename_namespace Foo Bar
•   delete_method
Delete "eat" method from "Food" class.
prt delete_method Food eat
•   move_class_method
Move "method" method in "Class" class to "another_method" method in "AnotherClass".  "Class"'s including packages are copied to "AnotherClass".
prt move_class_method 'Class#method' 'AnotherClass#another_method'
•   introduce_variables
Print the variables in the source code. This command accepts input from "STDIN".
prt introduce_variables a.pl cat a.pl | prt introduce_variables pbpaste | prt introduce_variables
You can specify the target files to refactor.
prt replace_token foo bar lib/**/**.pm t/*.t # Refactor Perl modules in lib/ and test files in t/
Without target files, "App::PRT" collects source codes in your project automatically.  "App::PRT" searches "cpanfile" to detect project root directory.  When executed in git repository, All files in the repository are used.
prt replace_token foo bar                    # Refactor the project in current working directory
Copyright (C) hitode909.
hitode909 <hitode909@gmail.com>
LLVM-CONFIG(1)                        LLVM                        LLVM-CONFIG(1)
llvm-config - Print LLVM compilation options
llvm-config option [components...]
llvm-config makes it easier to build applications that use LLVM.  It can print the compiler flags, linker flags and object libraries needed to link against LLVM.
To link against the JIT:
g++ `llvm-config --cxxflags` -o HowToUseJIT.o -c HowToUseJIT.cpp g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \ `llvm-config --libs engine bcreader scalaropts`
--version Print the version number of LLVM.
-help Print a summary of llvm-config arguments.
--prefix Print the installation prefix for LLVM.
--src-root Print the source root from which LLVM was built.
--obj-root Print the object root used to build LLVM.
--bindir Print the installation directory for LLVM binaries.
--includedir Print the installation directory for LLVM headers.
--libdir Print the installation directory for LLVM libraries.
--cxxflags Print the C++ compiler flags needed to use LLVM headers.
--ldflags Print the flags needed to link against LLVM libraries.
--libs Print all the libraries needed to link against the specified LLVM components, including any dependencies.
--libnames Similar to --libs, but prints the bare filenames of the libraries without -l or pathnames.  Useful for linking against a not-yet-installed copy of LLVM.
--libfiles Similar to --libs, but print the full path to each library file.  This is useful when creating makefile dependencies, to ensure that a tool is relinked if any library it uses changes.
--components Print all valid component names.
--targets-built Print the component names for all targets supported by this copy of LLVM.
--build-mode Print the build mode used when LLVM was built (e.g. Debug or Release)
To print a list of all available components, run llvm-config --components.  In most cases, components correspond directly to LLVM libraries.  Useful "virtual" components include:
all Includes all LLVM libraries.  The default if no components are specified.
backend Includes either a native backend or the C backend.
engine Includes either a native JIT or the bitcode interpreter.
If llvm-config succeeds, it will exit with 0.  Otherwise, if an error occurs, it will exit with a non-zero value.
XML-FORMAT(1)                General Commands Manual               XML-FORMAT(1)
XML-FORMAT - XML beautifier
xml-format filename
xml-format is an XML beautifier that indents and formats XML files for consistent line length.
As with all file beautifiers, its primary purpose is to take a document created by someone with a perplexing lack of self-discipline and aesthetic sensibility and make it readable.
The XML file is modified in place, and the original document is saved to filename.bak, in case you don't like the results.
Since XML is a class of markup languages, not a markup language, the type of each tag encountered is determined from the type of XML file (DocBook, XHTML, etc.), which, in turn, is inferred from the filename extension (".dbk" for DocBook, ".xhtml" for XHTML, etc.)
There are four types of tags:
Block tags denote blocks of content that should be visually separated from others in the XML source, and often require multiple lines, such as paragraphs, captions, and programlistings.  Blocks are separated from other content by a blank line.  Content within a block is indented the same as the block tags.
<para> The large forest planet Oglaroon is home to the Oglaroonians, an "intelligent" species who maintain an entire civilisation, including some extremely small wars, in one small nut tree, believing it to be the entire universe, and other trees to be merely Oglanut-induced illusions. </para>
Line tags denote small but important content items that should be highlighted, but not necessarily use multiple lines, such as titles and index terms.  xml-format attempts to keep line tag items to a single, separate line line.
<title>So Long, and Thanks for all the Fish</title>
Sectioning tags denote structural components of a document, such as chapters, sections, figures, and lists.  Opening and closing sectioning tags are placed alone on separate lines.  Content between sectioning tags is indented one more level beyond the tags themselves.
<chapter> <title>Construction of Earth</title>