35 lines
1.4 KiB
Bash
35 lines
1.4 KiB
Bash
|
Bash completion
|
||
|
|
===============
|
||
|
|
|
||
|
|
Environment variables
|
||
|
|
---------------------
|
||
|
|
|
||
|
|
*COMP_CONFIGURE_HINTS*::
|
||
|
|
If set and not null, `configure` completion will return the entire option
|
||
|
|
string (e.g. `--this-option=DESCRIPTION`) so one can see what kind of data
|
||
|
|
is required and then simply delete the descriptive text and add one's own
|
||
|
|
data. If unset or null (default), `configure` completion will strip
|
||
|
|
everything after the '=' when returning completions.
|
||
|
|
|
||
|
|
|
||
|
|
*COMP_CVS_REMOTE*::
|
||
|
|
If set and not null, `cvs commit` completion will try to complete on
|
||
|
|
remotely checked-out files. This requires passwordless access to the
|
||
|
|
remote repository. Default is unset.
|
||
|
|
|
||
|
|
|
||
|
|
*COMP_KNOWN_HOSTS_WITH_HOSTFILE*::
|
||
|
|
If set and not null (default), known_hosts completion will complement
|
||
|
|
hostnames from ssh's known_hosts_files with hostnames taken from the file
|
||
|
|
specified by the HOSTFILE shell variable (compgen -A hostname). If null,
|
||
|
|
known_hosts completion will omit hostnames from HOSTFILE. Omitting
|
||
|
|
hostnames from HOSTFILE is useful if HOSTFILE contains many entries for
|
||
|
|
local web development or ad-blocking.
|
||
|
|
|
||
|
|
|
||
|
|
*COMP_TAR_INTERNAL_PATHS*::
|
||
|
|
If set and not null *before* sourcing bash_completion, `tar` completion
|
||
|
|
will do correct path completion for tar file contents. If unset or null,
|
||
|
|
`tar' completion will do correct completion for paths to tar files. See
|
||
|
|
also README.
|