mirror of
https://github.com/cheat/cheat.git
synced 2024-11-01 05:31:01 +01:00
187 lines
4.8 KiB
Groff
187 lines
4.8 KiB
Groff
.\" Automatically generated by Pandoc 2.17.1.1
|
|
.\"
|
|
.\" Define V font for inline verbatim, using C font in formats
|
|
.\" that render this, and otherwise B font.
|
|
.ie "\f[CB]x\f[]"x" \{\
|
|
. ftr V B
|
|
. ftr VI BI
|
|
. ftr VB B
|
|
. ftr VBI BI
|
|
.\}
|
|
.el \{\
|
|
. ftr V CR
|
|
. ftr VI CI
|
|
. ftr VB CB
|
|
. ftr VBI CBI
|
|
.\}
|
|
.TH "CHEAT" "1" "" "" "General Commands Manual"
|
|
.hy
|
|
.SH NAME
|
|
.PP
|
|
\f[B]cheat\f[R] \[em] create and view command-line cheatsheets
|
|
.SH SYNOPSIS
|
|
.PP
|
|
\f[B]cheat\f[R] [options] [\f[I]CHEATSHEET\f[R]]
|
|
.SH DESCRIPTION
|
|
.PP
|
|
\f[B]cheat\f[R] allows you to create and view interactive cheatsheets on
|
|
the command-line.
|
|
It was designed to help remind *nix system administrators of options for
|
|
commands that they use frequently, but not frequently enough to
|
|
remember.
|
|
.SH OPTIONS
|
|
.TP
|
|
\[en]init
|
|
Print a config file to stdout.
|
|
.TP
|
|
-c, \[en]colorize
|
|
Colorize output.
|
|
.TP
|
|
-d, \[en]directories
|
|
List cheatsheet directories.
|
|
.TP
|
|
-e, \[en]edit=\f[I]CHEATSHEET\f[R]
|
|
Open \f[I]CHEATSHEET\f[R] for editing.
|
|
.TP
|
|
-l, \[en]list
|
|
List available cheatsheets.
|
|
.TP
|
|
-p, \[en]path=\f[I]PATH\f[R]
|
|
Filter only to sheets found on path \f[I]PATH\f[R].
|
|
.TP
|
|
-r, \[en]regex
|
|
Treat search \f[I]PHRASE\f[R] as a regular expression.
|
|
.TP
|
|
-s, \[en]search=\f[I]PHRASE\f[R]
|
|
Search cheatsheets for \f[I]PHRASE\f[R].
|
|
.TP
|
|
-t, \[en]tag=\f[I]TAG\f[R]
|
|
Filter only to sheets tagged with \f[I]TAG\f[R].
|
|
.TP
|
|
-T, \[en]tags
|
|
List all tags in use.
|
|
.TP
|
|
-v, \[en]version
|
|
Print the version number.
|
|
.TP
|
|
\[en]rm=\f[I]CHEATSHEET\f[R]
|
|
Remove (deletes) \f[I]CHEATSHEET\f[R].
|
|
.SH EXAMPLES
|
|
.TP
|
|
To view the foo cheatsheet:
|
|
cheat \f[I]foo\f[R]
|
|
.TP
|
|
To edit (or create) the foo cheatsheet:
|
|
cheat -e \f[I]foo\f[R]
|
|
.TP
|
|
To edit (or create) the foo/bar cheatsheet on the `work' cheatpath:
|
|
cheat -p \f[I]work\f[R] -e \f[I]foo/bar\f[R]
|
|
.TP
|
|
To view all cheatsheet directories:
|
|
cheat -d
|
|
.TP
|
|
To list all available cheatsheets:
|
|
cheat -l
|
|
.TP
|
|
To list all cheatsheets whose titles match `apt':
|
|
cheat -l \f[I]apt\f[R]
|
|
.TP
|
|
To list all tags in use:
|
|
cheat -T
|
|
.TP
|
|
To list available cheatsheets that are tagged as `personal':
|
|
cheat -l -t \f[I]personal\f[R]
|
|
.TP
|
|
To search for `ssh' among all cheatsheets, and colorize matches:
|
|
cheat -c -s \f[I]ssh\f[R]
|
|
.TP
|
|
To search (by regex) for cheatsheets that contain an IP address:
|
|
cheat -c -r -s \f[I]`(?:[0-9]{1,3}.){3}[0-9]{1,3}'\f[R]
|
|
.TP
|
|
To remove (delete) the foo/bar cheatsheet:
|
|
cheat \[en]rm \f[I]foo/bar\f[R]
|
|
.SH FILES
|
|
.SS Configuration
|
|
.PP
|
|
\f[B]cheat\f[R] is configured via a YAML file that is conventionally
|
|
named \f[I]conf.yaml\f[R].
|
|
\f[B]cheat\f[R] will search for \f[I]conf.yaml\f[R] in varying
|
|
locations, depending upon your platform:
|
|
.SS Linux, OSX, and other Unixes
|
|
.IP "1." 3
|
|
\f[B]CHEAT_CONFIG_PATH\f[R]
|
|
.IP "2." 3
|
|
\f[B]XDG_CONFIG_HOME\f[R]/cheat/conf.yaml
|
|
.IP "3." 3
|
|
\f[B]$HOME\f[R]/.config/cheat/conf.yml
|
|
.IP "4." 3
|
|
\f[B]$HOME\f[R]/.cheat/conf.yml
|
|
.SS Windows
|
|
.IP "1." 3
|
|
\f[B]CHEAT_CONFIG_PATH\f[R]
|
|
.IP "2." 3
|
|
\f[B]APPDATA\f[R]/cheat/conf.yml
|
|
.IP "3." 3
|
|
\f[B]PROGRAMDATA\f[R]/cheat/conf.yml
|
|
.PP
|
|
\f[B]cheat\f[R] will search in the order specified above.
|
|
The first \f[I]conf.yaml\f[R] encountered will be respected.
|
|
.PP
|
|
If \f[B]cheat\f[R] cannot locate a config file, it will ask if you\[cq]d
|
|
like to generate one automatically.
|
|
Alternatively, you may also generate a config file manually by running
|
|
\f[B]cheat \[en]init\f[R] and saving its output to the appropriate
|
|
location for your platform.
|
|
.SS Cheatpaths
|
|
.PP
|
|
\f[B]cheat\f[R] reads its cheatsheets from \[lq]cheatpaths\[rq], which
|
|
are the directories in which cheatsheets are stored.
|
|
Cheatpaths may be configured in \f[I]conf.yaml\f[R], and viewed via
|
|
\f[B]cheat -d\f[R].
|
|
.PP
|
|
For detailed instructions on how to configure cheatpaths, please refer
|
|
to the comments in conf.yml.
|
|
.SS Autocompletion
|
|
.PP
|
|
Autocompletion scripts for \f[B]bash\f[R], \f[B]zsh\f[R], and
|
|
\f[B]fish\f[R] are available for download:
|
|
.IP \[bu] 2
|
|
<https://github.com/cheat/cheat/blob/master/scripts/cheat.bash>
|
|
.IP \[bu] 2
|
|
<https://github.com/cheat/cheat/blob/master/scripts/cheat.fish>
|
|
.IP \[bu] 2
|
|
<https://github.com/cheat/cheat/blob/master/scripts/cheat.zsh>
|
|
.PP
|
|
The \f[B]bash\f[R] and \f[B]zsh\f[R] scripts provide optional
|
|
integration with \f[B]fzf\f[R], if the latter is available on your
|
|
\f[B]PATH\f[R].
|
|
.PP
|
|
The installation process will vary per system and shell configuration,
|
|
and thus will not be discussed here.
|
|
.SH ENVIRONMENT
|
|
.TP
|
|
\f[B]CHEAT_CONFIG_PATH\f[R]
|
|
The path at which the config file is available.
|
|
If \f[B]CHEAT_CONFIG_PATH\f[R] is set, all other config paths will be
|
|
ignored.
|
|
.TP
|
|
\f[B]CHEAT_USE_FZF\f[R]
|
|
If set, autocompletion scripts will attempt to integrate with
|
|
\f[B]fzf\f[R].
|
|
.SH RETURN VALUES
|
|
.IP "0." 3
|
|
Successful termination
|
|
.IP "1." 3
|
|
Application error
|
|
.IP "2." 3
|
|
Cheatsheet(s) not found
|
|
.SH BUGS
|
|
.PP
|
|
See GitHub issues: <https://github.com/cheat/cheat/issues>
|
|
.SH AUTHOR
|
|
.PP
|
|
Christopher Allen Lane <chris@chris-allen-lane.com>
|
|
.SH SEE ALSO
|
|
.PP
|
|
\f[B]fzf(1)\f[R]
|