neulab/tldr huggingface dataset:
extended versions of Heston model for the stochastic volatility of an asset including jumps.
References: A. Sepp, Pricing European-Style Options under Jump Diffusion Processes with Stochastic Volatility: Applications of Fourier Transform (http://math.ut.ee/~spartak/papers/stochjumpvols.pdf)
Tests calibration is tested against known values.
Examples: EquityOption.cpp.
Author Generated automatically by Doxygen for QuantLib from the source code.
GIT-UNDO(1)                        Git Extras                        GIT-UNDO(1)
git-undo - Remove latest commits
git-undo [<commitcount>] [-s, --soft, -h, --hard]
Removes the latest commits.
--soft or -s
This is the default, only rolls back the commit but changes remain un-staged.
--hard or -h
This option wipes your commit(s), so that your changes cannot be recovered. Use with care. To avoid being confused with --help, there will be a confirmation when -h is specified.
<commitcount>
Number of commits to remove. Defaults to 1, thus remove the latest commit.
Removes the latest commit.
$ git undo
Remove the latest 3 commits:
$ git undo 3
Written by Kenneth Reitz <me@kennethreitz.com> and Nick Lombard <github@jigsoft.co.za>
TEE(1P)                     POSIX Programmer's Manual                    TEE(1P)
tee — duplicate standard input
tee [-ai] [file...]
The tee utility shall copy standard input to standard output, making a copy in zero or more files. The tee utility shall not buffer output.
If the -a option is not specified, output files shall be written (see Section 1.1.1.4, File Read, Write, and Creation.
The tee utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-a        Append the output to the files.
-i        Ignore the SIGINT signal.
file      A pathname of an output file. If a file operand is '-', it shall refer to a file named -; implementations shall not treat it as meaning standard output.  Processing of at least 13 file operands shall be supported.
The standard input can be of any type.
The following environment variables shall affect the execution of tee:
Default, except that if the -i option was specified, SIGINT shall be ignored.
The standard output shall be a copy of the standard input.
If any file operands are specified, the standard input shall be copied to each named file.
0    The standard input was successfully copied to all output files.
If a write to any successfully opened file operand fails, writes to other successfully opened file operands and standard output shall continue, but the exit status shall be non-zero. Otherwise, the default actions specified in Section 1.4, Utility Description Defaults apply.
The tee utility is usually used in a pipeline, to make a copy of the output of some utility.
The file operand is technically optional, but tee is no more useful than cat when none is specified.
Save an unsorted intermediate form of the data in a pipeline:
... | tee unsorted | sort > sorted
The buffering requirement means that tee is not allowed to use ISO C standard fully buffered or line-buffered writes. It does not mean that tee has to do 1-byte reads followed by 1-byte writes.
It should be noted that early versions of BSD ignore any invalid options and accept a single '-' as an alternative to -i.  They also print a message if unable to open a file:
"tee: cannot access %s\n", <pathname>
Historical implementations ignore write errors. This is explicitly not permitted by this volume of POSIX.1‐2017.
Some historical implementations use O_APPEND when providing append mode; others use the lseek() function to seek to the end-of-file after opening the file without O_APPEND. This volume of POSIX.1‐2017 requires functionality equivalent to using O_APPEND; see Section 1.1.1.4, File Read, Write, and Creation.
Chapter 1, Introduction, cat
The System Interfaces volume of POSIX.1‐2017, lseek()
GO(1)                        General Commands Manual                       GO(1)
go-mod - module maintenance
go mod command [arguments]
Go mod provides access to operations on modules.
Note that support for modules is built into all the go commands, not just 'go mod'. For example, day-to-day adding, removing, upgrading, and downgrading of dependencies should be done using 'go get'.  See 'go help modules' for an overview of module functionality.
download download modules to local cache
edit   edit go.mod from tools or scripts
graph  print module requirement graph
init   initialize new module in current directory
tidy   add missing and remove unused modules
vendor make vendored copy of dependencies
verify verify dependencies have expected content
why    explain why packages or modules are needed
Use "go help mod <command>" for more information about a command.
This manual page and is maintained by the Debian Go Compiler Team <team+go-compiler@tracker.debian.org> based on the output of 'go help mod' for the Debian project (and may be used by others).
PATHCHK(1)                        User Commands                       PATHCHK(1)
pathchk - check whether file names are valid or portable
pathchk [OPTION]... NAME...
Diagnose invalid or unportable file names.
-p     check for most POSIX systems
-P     check for empty names and leading "-"
--portability check for all POSIX systems (equivalent to -p -P)
Written by Paul Eggert, David MacKenzie, and Jim Meyering.
Full documentation <https://www.gnu.org/software/coreutils/pathchk> or available locally via: info '(coreutils) pathchk invocation'
SEMVER(1)                                                              SEMVER(1)
semver - The semantic versioner for npm
Install npm install --save semver `
Usage As a node module:
const semver = require('semver')
semver.valid('1.2.3') // '1.2.3' semver.valid('a.b.c') // null semver.clean('  =v1.2.3   ') // '1.2.3' semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') // true semver.gt('1.2.3', '9.8.7') // false semver.lt('1.2.3', '9.8.7') // true semver.valid(semver.coerce('v2')) // '2.0.0' semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7'
As a command-line utility:
$ semver -h
SemVer 5.3.0
A JavaScript implementation of the http://semver.org/ specification Copyright Isaac Z. Schlueter
Usage: semver [options] <version> [<version> [...]] Prints valid versions sorted by SemVer precedence
Options: -r --range <range> Print versions that match the specified range.
-i --increment [<level>] Increment a version by the specified level.  Level can be one of: major, minor, patch, premajor, preminor, prepatch, or prerelease.  Default level is 'patch'. Only one version may be specified.
--preid <identifier> Identifier to be used to prefix premajor, preminor, prepatch or prerelease version increments.
-l --loose Interpret versions and ranges loosely
-c --coerce Coerce a string into SemVer if possible (does not imply --loose)
Program exits successfully if any valid version satisfies all supplied ranges, and prints all satisfying versions.
If no satisfying versions are found, then exits failure.
Versions are printed in ascending order, so supplying multiple versions to the utility will just sort them.
Versions A "version" is described by the v2.0.0 specification found at http://semver.org/.
A leading "=" or "v" character is stripped off and ignored.
Ranges A version range is a set of comparators which specify versions that satisfy the range.
A comparator is composed of an operator and a version.  The set of primitive operators is:
• < Less than
• <= Less than or equal to
• > Greater than
• >= Greater than or equal to
• = Equal.  If no operator is specified, then equality is assumed, so this operator is optional, but MAY be included.
For example, the comparator >=1.2.7 would match the versions 1.2.7, 1.2.8, 2.5.3, and 1.3.9, but not the versions 1.2.6 or 1.1.0.
Comparators can be joined by whitespace to form a comparator set, which is satisfied by the intersection of all of the comparators it includes.
A range is composed of one or more comparator sets, joined by ||.  A version matches a range if and only if every comparator in at least one of the ||-separated comparator sets is satisfied by the version.
For example, the range >=1.2.7 <1.3.0 would match the versions 1.2.7, 1.2.8, and 1.2.99, but not the versions 1.2.6, 1.3.0, or 1.1.0.
The range 1.2.7 || >=1.2.9 <2.0.0 would match the versions 1.2.7, 1.2.9, and 1.4.6, but not the versions 1.2.8 or 2.0.0.
Prerelease Tags If a version has a prerelease tag (for example, 1.2.3-alpha.3) then it will only be allowed to satisfy comparator sets if at least one comparator with the same [major, minor, patch] tuple also has a prerelease tag.
For example, the range >1.2.3-alpha.3 would be allowed to match the version 1.2.3-alpha.7, but it would not be satisfied by 3.4.5-alpha.9, even though 3.4.5-alpha.9 is technically "greater than" 1.2.3-alpha.3 according to the SemVer sort rules.  The version range only accepts prerelease tags on the 1.2.3 version.  The version 3.4.5 would satisfy the range, because it does not have a prerelease flag, and 3.4.5 is greater than 1.2.3-alpha.7.
The purpose for this behavior is twofold.  First, prerelease versions frequently are updated very quickly, and contain many breaking changes that are (by the author's design) not yet fit for public consumption. Therefore, by default, they are excluded from range matching semantics.
Second, a user who has opted into using a prerelease version has clearly indicated the intent to use that specific set of alpha/beta/rc versions. By including a prerelease tag in the range, the user is indicating that they are aware of the risk.  However, it is still not appropriate to assume that they have opted into taking a similar risk on the next set of prerelease versions.
Prerelease Identifiers The method .inc takes an additional identifier string argument that will append the value of the string as a prerelease identifier:
semver.inc('1.2.3', 'prerelease', 'beta') // '1.2.4-beta.0'
command-line example:
$ semver 1.2.3 -i prerelease --preid beta 1.2.4-beta.0
Which then can be used to increment further:
$ semver 1.2.4-beta.0 -i prerelease 1.2.4-beta.1
Advanced Range Syntax Advanced range syntax desugars to primitive comparators in deterministic ways.
Advanced ranges may be combined in the same way as primitive comparators using white space or ||.
Hyphen Ranges X.Y.Z - A.B.C Specifies an inclusive set.
• 1.2.3 - 2.3.4 := >=1.2.3 <=2.3.4
If a partial version is provided as the first version in the inclusive range, then the missing pieces are replaced with zeroes.
• 1.2 - 2.3.4 := >=1.2.0 <=2.3.4
If a partial version is provided as the second version in the inclusive range, then all versions that start with the supplied parts of the tuple are accepted, but nothing that would be greater than the provided tuple parts.
• 1.2.3 - 2.3 := >=1.2.3 <2.4.0
• 1.2.3 - 2 := >=1.2.3 <3.0.0
X-Ranges 1.2.x 1.X 1.2.* * Any of X, x, or * may be used to "stand in" for one of the numeric values in the [major, minor, patch] tuple.
• * := >=0.0.0 (Any version satisfies)
• 1.x := >=1.0.0 <2.0.0 (Matching major version)
• 1.2.x := >=1.2.0 <1.3.0 (Matching major and minor versions)
A partial version range is treated as an X-Range, so the special character is in fact optional.
• "" (empty string) := * := >=0.0.0
• 1 := 1.x.x := >=1.0.0 <2.0.0
• 1.2 := 1.2.x := >=1.2.0 <1.3.0
Tilde Ranges ~1.2.3 ~1.2 ~1 Allows patch-level changes if a minor version is specified on the comparator.  Allows minor-level changes if not.
• ~1.2.3 := >=1.2.3 <1.(2+1).0 := >=1.2.3 <1.3.0
• ~1.2 := >=1.2.0 <1.(2+1).0 := >=1.2.0 <1.3.0 (Same as 1.2.x)
• ~1 := >=1.0.0 <(1+1).0.0 := >=1.0.0 <2.0.0 (Same as 1.x)
• ~0.2.3 := >=0.2.3 <0.(2+1).0 := >=0.2.3 <0.3.0
• ~0.2 := >=0.2.0 <0.(2+1).0 := >=0.2.0 <0.3.0 (Same as 0.2.x)
• ~0 := >=0.0.0 <(0+1).0.0 := >=0.0.0 <1.0.0 (Same as 0.x)
• ~1.2.3-beta.2 := >=1.2.3-beta.2 <1.3.0 Note that prereleases in the 1.2.3 version will be allowed, if they are greater than or equal to beta.2.  So, 1.2.3-beta.4 would be allowed, but 1.2.4-beta.2 would not, because it is a prerelease of a different [major, minor, patch] tuple.
Caret Ranges ^1.2.3 ^0.2.5 ^0.0.4 Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple.  In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
Many authors treat a 0.x version as if the x were the major "breaking-change" indicator.
Caret ranges are ideal when an author may make breaking changes between 0.2.4 and 0.3.0 releases, which is a common practice.  However, it presumes that there will not be breaking changes between 0.2.4 and 0.2.5. It allows for changes that are presumed to be additive (but non-breaking), according to commonly observed practices.
• ^1.2.3 := >=1.2.3 <2.0.0
• ^0.2.3 := >=0.2.3 <0.3.0
• ^0.0.3 := >=0.0.3 <0.0.4
• ^1.2.3-beta.2 := >=1.2.3-beta.2 <2.0.0 Note that prereleases in the 1.2.3 version will be allowed, if they are greater than or equal to beta.2.  So, 1.2.3-beta.4 would be allowed, but 1.2.4-beta.2 would not, because it is a prerelease of a different [major, minor, patch] tuple.
• ^0.0.3-beta := >=0.0.3-beta <0.0.4  Note that prereleases in the 0.0.3 version only will be allowed, if they are greater than or equal to beta.  So, 0.0.3-pr.2 would be allowed.
When parsing caret ranges, a missing patch value desugars to the number 0, but will allow flexibility within that value, even if the major and minor versions are both 0.
• ^1.2.x := >=1.2.0 <2.0.0
• ^0.0.x := >=0.0.0 <0.1.0
• ^0.0 := >=0.0.0 <0.1.0
A missing minor and patch values will desugar to zero, but also allow flexibility within those values, even if the major version is zero.
• ^1.x := >=1.0.0 <2.0.0
• ^0.x := >=0.0.0 <1.0.0
Range Grammar Putting all this together, here is a Backus-Naur grammar for ranges, for the benefit of parser authors:
range-set  ::= range ( logical-or range ) * logical-or ::= ( ' ' ) * '||' ( ' ' ) * range      ::= hyphen | simple ( ' ' simple ) * | '' hyphen     ::= partial ' - ' partial simple     ::= primitive | partial | tilde | caret primitive  ::= ( '<' | '>' | '>=' | '<=' | '=' ) partial partial    ::= xr ( '.' xr ( '.' xr qualifier ? )? )? xr         ::= 'x' | 'X' | '*' | nr nr         ::= '0' | ['1'-'9'] ( ['0'-'9'] ) * tilde      ::= '~' partial caret      ::= '^' partial qualifier  ::= ( '-' pre )? ( '+' build )? pre        ::= parts build      ::= parts parts      ::= part ( '.' part ) * part       ::= nr | [-0-9A-Za-z]+
Functions All methods and classes take a final loose boolean argument that, if true, will be more forgiving about not-quite-valid semver strings.  The resulting output will always be 100% strict, of course.
Strict-mode Comparators and Ranges will be strict about the SemVer strings that they parse.
• valid(v): Return the parsed version, or null if it's not valid.
• inc(v, release): Return the version incremented by the release type (major,   premajor, minor, preminor, patch, prepatch, or prerelease), or null if it's not valid
• premajor in one call will bump the version up to the next major version and down to a prerelease of that major version.  preminor, and prepatch work the same way.
• If called from a non-prerelease version, the prerelease will work the same as prepatch. It increments the patch version, then makes a prerelease. If the input version is already a prerelease it simply increments it.
• prerelease(v): Returns an array of prerelease components, or null if none exist. Example: prerelease('1.2.3-alpha.1') -> ['alpha', 1]
• major(v): Return the major version number.
• minor(v): Return the minor version number.
• patch(v): Return the patch version number.
• intersects(r1, r2, loose): Return true if the two supplied ranges or comparators intersect.
Comparison • gt(v1, v2): v1 > v2
• gte(v1, v2): v1 >= v2
• lt(v1, v2): v1 < v2
• lte(v1, v2): v1 <= v2
• eq(v1, v2): v1 == v2 This is true if they're logically equivalent, even if they're not the exact same string.  You already know how to compare strings.
• neq(v1, v2): v1 != v2 The opposite of eq.
• cmp(v1, comparator, v2): Pass in a comparison string, and it'll call the corresponding function above.  "===" and "!==" do simple string comparison, but are included for completeness.  Throws if an invalid comparison string is provided.
• compare(v1, v2): Return 0 if v1 == v2, or 1 if v1 is greater, or -1 if v2 is greater.  Sorts in ascending order if passed to Array.sort().
• rcompare(v1, v2): The reverse of compare.  Sorts an array of versions in descending order when passed to Array.sort().
• diff(v1, v2): Returns difference between two versions by the release type (major, premajor, minor, preminor, patch, prepatch, or prerelease), or null if the versions are the same.
Comparators • intersects(comparator): Return true if the comparators intersect
Ranges • validRange(range): Return the valid range or null if it's not valid
• satisfies(version, range): Return true if the version satisfies the range.
• maxSatisfying(versions, range): Return the highest version in the list that satisfies the range, or null if none of them do.
• minSatisfying(versions, range): Return the lowest version in the list that satisfies the range, or null if none of them do.
• gtr(version, range): Return true if version is greater than all the versions possible in the range.
• ltr(version, range): Return true if version is less than all the versions possible in the range.
• outside(version, range, hilo): Return true if the version is outside the bounds of the range in either the high or low direction.  The hilo argument must be either the string '>' or '<'.  (This is the function called by gtr and ltr.)
• intersects(range): Return true if any of the ranges comparators intersect
Note that, since ranges may be non-contiguous, a version might not be greater than a range, less than a range, or satisfy a range!  For example, the range 1.2 <1.2.9 || >2.0.0 would have a hole from 1.2.9 until 2.0.0, so the version 1.2.10 would not be greater than the range (because 2.0.1 satisfies, which is higher), nor less than the range (since 1.2.8 satisfies, which is lower), and it also does not satisfy the range.
If you want to know if a version satisfies or does not satisfy a range, use the satisfies(version, range) function.
Coercion • coerce(version): Coerces a string to semver if possible
This aims to provide a very forgiving translation of a non-semver string to semver. It looks for the first digit in a string, and consumes all remaining characters which satisfy at least a partial semver (e.g., 1, 1.2, 1.2.3) up to the max permitted length (256 characters).  Longer versions are simply truncated (4.6.3.9.2-alpha2 becomes 4.6.3).  All surrounding text is simply ignored (v3.4 replaces v3.3.1 becomes 3.4.0). Only text which lacks digits will fail coercion (version one is not valid).  The maximum  length for any semver component considered for coercion is 16 characters; longer components will be ignored (10000000000000000.4.7.4 becomes 4.7.4).  The maximum value for any semver component is Integer.MAX_SAFE_INTEGER || (2**53 - 1); higher value components are invalid (9999999999999999.4.7.4 is likely invalid).
NEOFETCH(1)                       User Commands                      NEOFETCH(1)
Neofetch - A fast, highly customizable system info script
neofetch func_name --option "value" --option "value"
Neofetch is a CLI system information tool written in BASH. Neofetch displays information about your system next to an image, your OS logo, or any ASCII file of your choice.
NOTE: Every launch flag has a config option.
INFO: func_name Specify a function name (second part of info() from config) to quickly display only that function's information.
Example: neofetch uptime --uptime_shorthand tiny
Example: neofetch uptime disk wm memory
This can be used in bars and scripts like so:
memory="$(neofetch memory)"; memory="${memory##*: }"
For multiple outputs at once (each line of info in an array):
IFS=$'\n' read -d "" -ra info < <(neofetch memory uptime wm)
info=("${info[@]##*: }")
--disable infoname Allows you to disable an info line from appearing in the output. 'infoname' is the function name from the 'print_info()' function inside the config file.  For example: 'info "Memory" memory' would be '--disable memory'
NOTE: You can supply multiple args. eg. 'neofetch --disable cpu gpu'
--title_fqdn on/off Hide/Show Fully Qualified Domain Name in title.
--package_managers on/off Hide/Show Package Manager names . (on, tiny, off)
--os_arch on/off Hide/Show OS architecture.
--speed_type type Change the type of cpu speed to display.  Possible values: current, min, max, bios, scaling_current, scaling_min, scaling_max
NOTE: This only supports Linux with cpufreq.
--speed_shorthand on/off Whether or not to show decimals in CPU speed.
NOTE: This flag is not supported in systems with CPU speed less than 1 GHz.
--cpu_brand on/off Enable/Disable CPU brand in output.
--cpu_cores type Whether or not to display the number of CPU cores Possible values: logical, physical, off
NOTE: 'physical' doesn't work on BSD.
--cpu_speed on/off Hide/Show cpu speed.
--cpu_temp C/F/off Hide/Show cpu temperature.
NOTE: This only works on Linux and BSD.
NOTE: For FreeBSD and NetBSD-based systems, you need to enable coretemp kernel module. This only supports newer Intel processors.
--distro_shorthand on/off Shorten the output of distro (on, tiny, off)
NOTE: This option won't work in Windows (Cygwin)
--kernel_shorthand on/off Shorten the output of kernel
NOTE: This option won't work in BSDs (except PacBSD and PC-BSD)
--uptime_shorthand on/off Shorten the output of uptime (on, tiny, off)
--refresh_rate on/off Whether to display the refresh rate of each monitor Unsupported on Windows
--gpu_brand on/off Enable/Disable GPU brand in output. (AMD/NVIDIA/Intel)
--gpu_type type Which GPU to display. (all, dedicated, integrated)
NOTE: This only supports Linux.
--de_version on/off Show/Hide Desktop Environment version
--gtk_shorthand on/off Shorten output of gtk theme/icons
--gtk2 on/off Enable/Disable gtk2 theme/font/icons output
--gtk3 on/off Enable/Disable gtk3 theme/font/icons output
--shell_path on/off Enable/Disable showing $SHELL path
--shell_version on/off Enable/Disable showing $SHELL version
--disk_show value Which disks to display.  Possible values: '/', '/dev/sdXX', '/path/to/mount point'
NOTE: Multiple values can be given. (--disk_show '/' '/dev/sdc1')
--disk_subtitle type What information to append to the Disk subtitle.  Takes: name, mount, dir, none
'name' shows the disk's name (sda1, sda2, etc)
'mount' shows the disk's mount point (/, /mnt/Local Disk, etc)
'dir' shows the basename of the disks's path. (/, Local Disk, etc)
'none' shows only 'Disk' or the configured title.
--disk_percent on/off Hide/Show disk percent.
--ip_host url URL to query for public IP
--ip_timeout int Public IP timeout (in seconds).
--song_format format Print the song data in a specific format (see config file).
--song_shorthand on/off Print the Artist/Album/Title on separate lines.
--memory_percent on/off Display memory percentage.
--music_player player-name Manually specify a player to use.  Available values are listed in the config file
TEXT FORMATTING: --colors x x x x x x Changes the text colors in this order: title, @, underline, subtitle, colon, info
--underline on/off Enable/Disable the underline.
--underline_char char Character to use when underlining title
--bold on/off Enable/Disable bold text
--separator string Changes the default ':' separator to the specified string.
COLOR BLOCKS: --color_blocks on/off Enable/Disable the color blocks
--col_offset auto/num Left-padding of color blocks
--block_width num Width of color blocks in spaces
--block_height num Height of color blocks in lines
--block_range num num Range of colors to print as blocks
BARS: --bar_char 'elapsed char' 'total char' Characters to use when drawing bars.
--bar_border on/off Whether or not to surround the bar with '[]'
--bar_length num Length in spaces to make the bars.
--bar_colors num num Colors to make the bar.  Set in this order: elapsed, total
--cpu_display mode Bar mode.  Possible values: bar, infobar, barinfo, off
--memory_display mode Bar mode.  Possible values: bar, infobar, barinfo, off
--battery_display mode Bar mode.  Possible values: bar, infobar, barinfo, off
--disk_display mode Bar mode.  Possible values: bar, infobar, barinfo, off
IMAGE BACKEND: --backend backend Which image backend to use.  Possible values: 'ascii', 'caca', 'chafa', 'jp2a', 'iterm2', 'off', 'sixel', 'tycat', 'w3m', 'kitty'
--source source Which image or ascii file to use.  Possible values: 'auto', 'ascii', 'wallpaper', '/path/to/img', '/path/to/ascii', '/path/to/dir/', 'command output' [ascii]
--ascii source Shortcut to use 'ascii' backend.
NEW: neofetch --ascii "$(fortune | cowsay -W 30)"
--caca source Shortcut to use 'caca' backend.
--chafa source Shortcut to use 'chafa' backend.
--iterm2 source Shortcut to use 'iterm2' backend.
--jp2a source Shortcut to use 'jp2a' backend.
--kitty source Shortcut to use 'kitty' backend.
--pixterm source Shortcut to use 'pixterm' backend.
--sixel source Shortcut to use 'sixel' backend.
--termpix source Shortcut to use 'termpix' backend.
--tycat source Shortcut to use 'tycat' backend.
--w3m source Shortcut to use 'w3m' backend.
--off  Shortcut to use 'off' backend (Disable ascii art).
NOTE: 'source; can be any of the following: 'auto', 'ascii', 'wallpaper', '/path/to/img', '/path/to/ascii', '/path/to/dir/'
ASCII: --ascii_colors x x x x x x Colors to print the ascii art
--ascii_distro distro Which Distro's ascii art to print
NOTE: AIX, Alpine, AlterLinux, Anarchy, Android, Antergos, antiX, "AOSC OS", "AOSC OS/Retro", Apricity, ArcoLinux, ArchBox, ARCHlabs, ArchStrike, XFerience, ArchMerge, Arch, Artix, Arya, Bedrock, Bitrig, BlackArch, BLAG, BlankOn, BlueLight, bonsai, BSD, BunsenLabs, Calculate, Carbs, CentOS, Chakra, ChaletOS, Chapeau, Chrom, Cleanjaro, ClearOS, Clear_Linux, Clover, Condres, Container_Linux, CRUX, Cucumber, Debian, Deepin, DesaOS, Devuan, DracOS, DragonFly, Drauger, Elementary, EndeavourOS, Endless, EuroLinux, Exherbo, Fedora, Feren, FreeBSD, FreeMiNT, Frugalware, Funtoo, GalliumOS, Gentoo, Pentoo, gNewSense, GNOME, GNU, GoboLinux, Grombyang, Guix, Haiku, Huayra, Hyperbola, janus, Kali, KaOS, KDE_neon, Kibojoe, Kogaion, Korora, KSLinux, Kubuntu, LEDE, LFS, Linux_Lite, LMDE, Lubuntu, Lunar, macos, Mageia, MagpieOS, Mandriva, Manjaro, Maui, Mer, Minix, LinuxMint, MX_Linux, Namib, Neptune, NetBSD, Netrunner, Nitrux, NixOS, Nurunner, NuTyX, OBRevenge, OpenBSD, OpenIndiana, openmamba, OpenMandriva, OpenStage, OpenWrt, osmc, Oracle, OS Elbrus, PacBSD, Parabola, Pardus, Parrot, Parsix, TrueOS, PCLinuxOS, Peppermint, popos, Porteus, PostMarketOS, Proxmox, Puppy, PureOS, Qubes, Radix, Raspbian, Reborn_OS, Redstar, Redcore, Redhat, Refracted_Devuan, Regata, Rosa, sabotage, Sabayon, Sailfish, SalentOS, Scientific, Septor, SereneLinux, SharkLinux, Siduction, Slackware, SliTaz, SmartOS, Solus, Source_Mage, Sparky, Star, SteamOS, SunOS, openSUSE_Leap, openSUSE_Tumbleweed, openSUSE, SwagArch, Tails, Trisquel, Ubuntu-Budgie, Ubuntu-GNOME, Ubuntu-MATE, Ubuntu-Studio, Ubuntu, Venom, Void, Obarun, windows10, Windows7, Xubuntu, Zorin, and IRIX have ascii logos
NOTE: Arch, Ubuntu, Redhat, and Dragonfly have 'old' logo variants.
NOTE: Use '{distro name}_old' to use the old logos.
NOTE: Ubuntu has flavor variants.
NOTE: Change this to Lubuntu, Kubuntu, Xubuntu, Ubuntu-GNOME, Ubuntu-Studio, Ubuntu-Mate  or Ubuntu-Budgie to use the flavors.
NOTE: Arcolinux, Dragonfly, Fedora, Alpine, Arch, Ubuntu, CRUX, Debian, Gentoo, FreeBSD, Mac, NixOS, OpenBSD, android, Antrix, CentOS, Cleanjaro, ElementaryOS, GUIX, Hyperbola, Manjaro, MXLinux, NetBSD, Parabola, POP_OS, PureOS, Slackware, SunOS, LinuxLite, OpenSUSE, Raspbian, postmarketOS, and Void have a smaller logo variant.
NOTE: Use '{distro name}_small' to use the small variants.
--ascii_bold on/off Whether or not to bold the ascii logo.
-L, --logo Hide the info text and only show the ascii logo.
IMAGE: --loop Redraw the image constantly until Ctrl+C is used. This fixes issues in some terminals emulators when using image mode.
--size 00px | --size 00% How to size the image.  Possible values: auto, 00px, 00%, none
--crop_mode mode Which crop mode to use Takes the values: normal, fit, fill
--crop_offset value Change the crop offset for normal mode.  Possible values: northwest, north, northeast, west, center, east, southwest, south, southeast
--xoffset px How close the image will be to the left edge of the window. This only works with w3m.
--yoffset px How close the image will be to the top edge of the window. This only works with w3m.
--bg_color color Background color to display behind transparent image.  This only works with w3m.
--gap num Gap between image and text.
NOTE: --gap can take a negative value which will move the text closer to the left side.
--clean Delete cached files and thumbnails.
OTHER: --config /path/to/config Specify a path to a custom config file
--config none Launch the script without a config file
--no_config Don't create the user config file.
--print_config Print the default config file to stdout.
--stdout Turn off all colors and disables any ASCII/image backend.
--help Print this text and exit
--version Show neofetch version
-v     Display error messages.
-vv    Display a verbose log for error reporting.
DEVELOPER: --gen-man Generate a manpage for Neofetch in your PWD. (Requires GNU help2man)
Report bugs to https://github.com/dylanaraps/neofetch/issues
MONGORESTORE(1)              General Commands Manual             MONGORESTORE(1)
mongorestore - restore backups generated with mongodump(1)
mongorestore [options] [directory or file to restore]
The mongorestore program allows restoring backups obtained using mongodump(1) into a running MongoDB instance. By default it will restore all data in the specified file or directory, but limitting by database and collection is possible.
See mongorestore --help for a list supported options and their descriptions.
mongodump(1)
The full documentation of mongorestore can be found at https://docs.mongodb.com/manual/reference/program/mongorestore/.
mongorestore was written by MongoDB, Inc. and is licensed under the Apache License, Version 2.0.
COLUMN(1)                         User Commands                        COLUMN(1)
column - columnate lists
column [options] [file ...]
The column utility formats its input into multiple columns. The util support three modes:
columns are filled before rows This is the default mode (required by backward compatibility).
rows are filled before columns This mode is enabled by option -x, --fillrows
table Determine the number of columns the input contains and create a table. This mode is enabled by option -t, --table and columns formatting is possible to modify by --table-* options. Use this mode if not sure.
Input is taken from file, or otherwise from standard input. Empty lines are ignored and all invalid multibyte sequences are encoded by x<hex> convention.
The argument columns for --table-* options is a comma separated list of the column names as defined by --table-columns or it’s column number in order as specified by input. It’s possible to mix names and numbers. The special placeholder '0' (e.g. -R0) may be used to specify all columns.
-J, --json Use JSON output format to print the table, the option --table-columns is required and the option --table-name is recommended.
-c, --output-width width Output is formatted to a width specified as number of characters. The original name of this option is --columns; this name is deprecated since v2.30. Note that input longer than width is not truncated by default.
-d, --table-noheadings Do not print header. This option allows the use of logical column names on the command line, but keeps the header hidden when printing the table.
-o, --output-separator string Specify the columns delimiter for table output (default is two spaces).
-s, --separator separators Specify the possible input item delimiters (default is whitespace).
-t, --table Determine the number of columns the input contains and create a table. Columns are delimited with whitespace, by default, or with the characters supplied using the --output-separator option. Table output is useful for pretty-printing.
-N, --table-columns names Specify the columns names by comma separated list of names. The names are used for the table header or to address column in option arguments.
-l, --table-columns-limit number Specify maximal number of the input columns. The last column will contain all remaining line data if the limit is smaller than the number of the columns in the input data.
-R, --table-right columns Right align text in the specified columns.
-T, --table-truncate columns Specify columns where text can be truncated when necessary, otherwise very long table entries may be printed on multiple lines.
-E, --table-noextreme columns Specify columns where is possible to ignore unusually long (longer than average) cells when calculate column width. The option has impact to the width calculation and table formatting, but the printed text is not affected.
The option is used for the last visible column by default.
-e, --table-header-repeat Print header line for each page.
-W, --table-wrap columns Specify columns where is possible to use multi-line cell for long text when necessary.
-H, --table-hide columns Don’t print specified columns. The special placeholder '-' may be used to hide all unnamed columns (see --table-columns).
-O, --table-order columns Specify columns order on output.
-n, --table-name name Specify the table name used for JSON output. The default is "table".
-L, --keep-empty-lines Preserve whitespace-only lines in the input. The default is ignore empty lines at all. This option’s original name was --table-empty-lines but is now deprecated because it gives the false impression that the option only applies to table mode.
-r, --tree column Specify column to use tree-like output. Note that the circular dependencies and other anomalies in child and parent relation are silently ignored.
-i, --tree-id column Specify column with line ID to create child-parent relation.
-p, --tree-parent column Specify column with parent ID to create child-parent relation.
-x, --fillrows Fill rows before filling columns.
The environment variable COLUMNS is used to determine the size of the screen if no other information is available.
The column command appeared in 4.3BSD-Reno.
Version 2.23 changed the -s option to be non-greedy, for example:
printf "a:b:c\n1::3\n" | column -t -s ':'
Old output:
a  b  c 1  3
New output (since util-linux 2.23):
a  b  c 1     3
Historical versions of this tool indicated that "rows are filled before columns" by default, and that the -x option reverses this. This wording did not reflect the actual behavior, and it has since been corrected (see above). Other implementations of column may continue to use the older documentation, but the behavior should be identical in any case.
Print fstab with header line and align number to the right:
sed 's/#.*//' /etc/fstab | column --table --table-columns SOURCE,TARGET,TYPE,OPTIONS,PASS,FREQ --table-right PASS,FREQ
Print fstab and hide unnamed columns:
sed 's/#.*//' /etc/fstab | column --table --table-columns SOURCE,TARGET,TYPE --table-hide -
Print a tree:
echo -e '1 0 A\n2 1 AA\n3 1 AB\n4 2 AAA\n5 2 AAB' | column --tree-id 1 --tree-parent 2 --tree 3 1  0  A 2  1  |-AA 4  2  | |-AAA 5  2  | `-AAB 3  1  `-AB
colrm(1), ls(1), paste(1), sort(1)
The column 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/>.
A2QUERY.IN(1)          User Contributed Perl Documentation         A2QUERY.IN(1)
a2query - retrieve runtime configuration from a local Apache 2 HTTP server
a2query  [-m [MODULE]] [-s [SITE]] [-c [CONF]] [-a] [-v] [-M] [-d] [-h]
a2query is a program designed to retrieve configuration values from a locally available Apache 2 HTTP web server. It was designed to be as robust as possible by returning feasible values even if the Apache 2 syntax validator fails.
This program is primarily meant to be used from maintainer scripts.
-a  Returns the Apache 2 "Module Magic Version" (API version) number, the server was compiled with. The returned version does not contain any minor versions which are known to be compatible with the major version returned.
-c [CONF] Checks whether the configuration CONF is enabled. If no argument was given, all enabled configuration files are being returned. CONF is compared by string comparison by ignoring a leading "mod_" prefix and possibly a '.conf' or '.load' suffix.
-h  Displays a brief summary how the program can be called and exits.
-m [MODULE] Checks whether the module MODULE is enabled, The argument is interpreted in the same way, as for configuration files queried by the -c switch.
-M  Returns the currently enabled Apache 2 MPM (Multi Processing Module).
-s [SITE] Checks whether the module SITE is enabled, The argument is interpreted in the same way, as for configuration files queried by the -c switch.
-v  returns the currently installed Apache 2 HTTP server version
-q  suppress any output. This is useful to invoke a2query from another script. This is useful if only the return code is of interest.
a2query returns with a zero (0) exit status if the requested operation was effectuated successfully and with a non-zero status otherwise. In case of an error it leaves with error code 32 if a requested module, site or configuration was not found and 33 if a module, site or configuration was disabled by a maintainer script. However, exit status 1 is returned if the module was not found at all
apache2ctl(8), apache2(8), perl(1)
This manual and a2query was written by Arno Toell <debian@toell.net>.
qdbus(1)                          User commands                         qdbus(1)
qdbus - a communication-interface for qt-based applications
qdbus [--system] [--literal] [servicename] [path] [method] [args]
qdbus provides an interface to Qt-based applications communicating over D-Bus.  See http://www.freedesktop.org/software/dbus/ for more information about the big picture.
By default qdbus will list all service names of services that are running and you can manipulate at the moment.  You can also manipulate and run several types of methods for each dbus-enabled application.
servicename the service to connect to (e.g., org.freedesktop.DBus)
path   the path to the object (e.g., /)
method the method to call, with or without the interface
args   arguments to pass to the call
--system connect to the system bus
--literal print replies literally
Here is an example of using qdbus to list all status information about a service: % qdbus org.ktorrent.ktorrent
dbus-cleanup-sockets(1), dbus-launch(1), dbus-send(1), dbus-daemon(1), dbus-monitor(1), dbus-uuidgen(1)
GIT-MERGE(1)                       Git Manual                       GIT-MERGE(1)
git-merge - Join two or more development histories together
git merge [-n] [--stat] [--no-commit] [--squash] [--[no-]edit] [--no-verify] [-s <strategy>] [-X <strategy-option>] [-S[<keyid>]] [--[no-]allow-unrelated-histories] [--[no-]rerere-autoupdate] [-m <msg>] [-F <file>] [<commit>...] git merge (--continue | --abort | --quit)
Incorporates changes from the named commits (since the time their histories diverged from the current branch) into the current branch. This command is used by git pull to incorporate changes from another repository and can be used by hand to merge changes from one branch into another.
Assume the following history exists and the current branch is "master":
Then "git merge topic" will replay the changes made on the topic branch since it diverged from master (i.e., E) until its current commit (C) on top of master, and record the result in a new commit along with the names of the two parent commits and a log message from the user describing the changes.
A---B---C topic /         \ D---E---F---G---H master
The second syntax ("git merge --abort") can only be run after the merge has resulted in conflicts. git merge --abort will abort the merge process and try to reconstruct the pre-merge state. However, if there were uncommitted changes when the merge started (and especially if those changes were further modified after the merge was started), git merge --abort will in some cases be unable to reconstruct the original (pre-merge) changes. Therefore:
Warning: Running git merge with non-trivial uncommitted changes is discouraged: while possible, it may leave you in a state that is hard to back out of in the case of a conflict.
The third syntax ("git merge --continue") can only be run after the merge has resulted in conflicts.
--commit, --no-commit Perform the merge and commit the result. This option can be used to override --no-commit.
With --no-commit perform the merge and stop just before creating a merge commit, to give the user a chance to inspect and further tweak the merge result before committing.
Note that fast-forward updates do not create a merge commit and therefore there is no way to stop those merges with --no-commit. Thus, if you want to ensure your branch is not changed or updated by the merge command, use --no-ff with --no-commit.
--edit, -e, --no-edit Invoke an editor before committing successful mechanical merge to further edit the auto-generated merge message, so that the user can explain and justify the merge. The --no-edit option can be used to accept the auto-generated message (this is generally discouraged). The --edit (or -e) option is still useful if you are giving a draft message with the -m option from the command line and want to edit it in the editor.
Older scripts may depend on the historical behaviour of not allowing the user to edit the merge log message. They will see an editor opened when they run git merge. To make it easier to adjust such scripts to the updated behaviour, the environment variable GIT_MERGE_AUTOEDIT can be set to no at the beginning of them.
--cleanup=<mode> This option determines how the merge message will be cleaned up before committing. See git-commit(1) for more details. In addition, if the <mode> is given a value of scissors, scissors will be appended to MERGE_MSG before being passed on to the commit machinery in the case of a merge conflict.
--ff, --no-ff, --ff-only Specifies how a merge is handled when the merged-in history is already a descendant of the current history.  --ff is the default unless merging an annotated (and possibly signed) tag that is not stored in its natural place in the refs/tags/ hierarchy, in which case --no-ff is assumed.
With --ff, when possible resolve the merge as a fast-forward (only update the branch pointer to match the merged branch; do not create a merge commit). When not possible (when the merged-in history is not a descendant of the current history), create a merge commit.
With --no-ff, create a merge commit in all cases, even when the merge could instead be resolved as a fast-forward.
With --ff-only, resolve the merge as a fast-forward when possible. When not possible, refuse to merge and exit with a non-zero status.
-S[<keyid>], --gpg-sign[=<keyid>], --no-gpg-sign GPG-sign the resulting merge commit. The keyid argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space.  --no-gpg-sign is useful to countermand both commit.gpgSign configuration variable, and earlier --gpg-sign.
--log[=<n>], --no-log In addition to branch names, populate the log message with one-line descriptions from at most <n> actual commits that are being merged. See also git-fmt-merge-msg(1).
With --no-log do not list one-line descriptions from the actual commits being merged.
--signoff, --no-signoff Add a Signed-off-by trailer by the committer at the end of the commit log message. The meaning of a signoff depends on the project to which you’re committing. For example, it may certify that the committer has the rights to submit the work under the project’s license or agrees to some contributor representation, such as a Developer Certificate of Origin. (See http://developercertificate.org for the one used by the Linux kernel and Git projects.) Consult the documentation or leadership of the project to which you’re contributing to understand how the signoffs are used in that project.
The --no-signoff option can be used to countermand an earlier --signoff option on the command line.
--stat, -n, --no-stat Show a diffstat at the end of the merge. The diffstat is also controlled by the configuration option merge.stat.
With -n or --no-stat do not show a diffstat at the end of the merge.
--squash, --no-squash Produce the working tree and index state as if a real merge happened (except for the merge information), but do not actually make a commit, move the HEAD, or record $GIT_DIR/MERGE_HEAD (to cause the next git commit command to create a merge commit). This allows you to create a single commit on top of the current branch whose effect is the same as merging another branch (or more in case of an octopus).
With --no-squash perform the merge and commit the result. This option can be used to override --squash.
With --squash, --commit is not allowed, and will fail.
--[no-]verify By default, the pre-merge and commit-msg hooks are run. When --no-verify is given, these are bypassed. See also githooks(5).
-s <strategy>, --strategy=<strategy> Use the given merge strategy; can be supplied more than once to specify them in the order they should be tried. If there is no -s option, a built-in list of strategies is used instead (ort when merging a single head, octopus otherwise).
-X <option>, --strategy-option=<option> Pass merge strategy specific option through to the merge strategy.
--verify-signatures, --no-verify-signatures Verify that the tip commit of the side branch being merged is signed with a valid key, i.e. a key that has a valid uid: in the default trust model, this means the signing key has been signed by a trusted key. If the tip commit of the side branch is not signed with a valid key, the merge is aborted.
--summary, --no-summary Synonyms to --stat and --no-stat; these are deprecated and will be removed in the future.
-q, --quiet Operate quietly. Implies --no-progress.
--progress, --no-progress Turn progress on/off explicitly. If neither is specified, progress is shown if standard error is connected to a terminal. Note that not all merge strategies may support progress reporting.
--autostash, --no-autostash Automatically create a temporary stash entry before the operation begins, record it in the special ref MERGE_AUTOSTASH and apply it after the operation ends. This means that you can run the operation on a dirty worktree. However, use with care: the final stash application after a successful merge might result in non-trivial conflicts.
--allow-unrelated-histories By default, git merge command refuses to merge histories that do not share a common ancestor. This option can be used to override this safety when merging histories of two projects that started their lives independently. As that is a very rare occasion, no configuration variable to enable this by default exists and will not be added.
-m <msg> Set the commit message to be used for the merge commit (in case one is created).
If --log is specified, a shortlog of the commits being merged will be appended to the specified message.
The git fmt-merge-msg command can be used to give a good default for automated git merge invocations. The automated message can include the branch description.
-F <file>, --file=<file> Read the commit message to be used for the merge commit (in case one is created).
--overwrite-ignore, --no-overwrite-ignore Silently overwrite ignored files from the merge result. This is the default behavior. Use --no-overwrite-ignore to abort.
--abort Abort the current conflict resolution process, and try to reconstruct the pre-merge state. If an autostash entry is present, apply it to the worktree.
If there were uncommitted worktree changes present when the merge started, git merge --abort will in some cases be unable to reconstruct these changes. It is therefore recommended to always commit or stash your changes before running git merge.
git merge --abort is equivalent to git reset --merge when MERGE_HEAD is present unless MERGE_AUTOSTASH is also present in which case git merge --abort applies the stash entry to the worktree whereas git reset --merge will save the stashed changes in the stash list.
--quit Forget about the current merge in progress. Leave the index and the working tree as-is. If MERGE_AUTOSTASH is present, the stash entry will be saved to the stash list.
--continue After a git merge stops due to conflicts you can conclude the merge by running git merge --continue (see "HOW TO RESOLVE CONFLICTS" section below).