fish-shell/doc_src/cmds/complete.rst

.. _cmd-complete:

complete - edit command specific tab-completions
================================================

Synopsis
--------

``complete`` **-c** | **--command** | **-p** | **--path** [*options*] *COMMAND*
``complete`` **-C** *STRING* | **--do-complete** *STRING*

Description
-----------

``complete`` defines, removes or lists completions for a command.

For an introduction to writing your own completions, see :ref:`Writing your own completions <completion-own>` in
the fish manual.

- ``-c COMMAND`` or ``--command COMMAND`` specifies that ``COMMAND`` is the name of the command. If there is no ``-c`` or ``-p``, one non-option argument will be used as the command.

- ``-p COMMAND`` or ``--path COMMAND`` specifies that ``COMMAND`` is the absolute path of the command (optionally containing wildcards).

- ``-e`` or ``--erase`` deletes the specified completion.

- ``-s SHORT_OPTION`` or ``--short-option=SHORT_OPTION`` adds a short option to the completions list.

- ``-l LONG_OPTION`` or ``--long-option=LONG_OPTION`` adds a GNU style long option to the completions list.

- ``-o LONG_OPTION`` or ``--old-option=LONG_OPTION`` adds an old style long option to the completions list (See below for details).

- ``-a ARGUMENTS`` or ``--arguments=ARGUMENTS`` adds the specified option arguments to the completions list.

- ``-k`` or ``--keep-order`` keeps the order of ``ARGUMENTS`` instead of sorting alphabetically. Multiple ``complete`` calls with ``-k`` result in arguments of the later ones displayed first.

- ``-f`` or ``--no-files`` says that this completion may not be followed by a filename.

- ``-F`` or ``--force-files`` says that this completion may be followed by a filename, even if another applicable ``complete`` specified ``--no-files``.

- ``-r`` or ``--require-parameter`` says that this completion must have an option argument, i.e. may not be followed by another option.

- ``-x`` or ``--exclusive`` is short for ``-r`` and ``-f``.

- ``-w WRAPPED_COMMAND`` or ``--wraps=WRAPPED_COMMAND`` causes the specified command to inherit completions from the wrapped command (See below for details).

- ``-n CONDITION`` or ``--condition CONDITION`` specifies that this completion should only be used if the CONDITION (a shell command) returns 0. This makes it possible to specify completions that should only be used in some cases.

- ``-C STRING`` or ``--do-complete=STRING`` makes complete try to find all possible completions for the specified string. If there is no STRING, the current commandline is used instead.

Command specific tab-completions in ``fish`` are based on the notion of options and arguments. An option is a parameter which begins with a hyphen, such as ``-h``, ``-help`` or ``--help``. Arguments are parameters that do not begin with a hyphen. Fish recognizes three styles of options, the same styles as the GNU getopt library. These styles are:

- Short options, like ``-a``. Short options are a single character long, are preceded by a single hyphen and can be grouped together (like ``-la``, which is equivalent to ``-l -a``). Option arguments may be specified by appending the option with the value (``-w32``), or, if ``--require-parameter`` is given, in the following parameter (``-w 32``).

- Old style long options, like ``-Wall`` or ``-name``. Old style long options can be more than one character long, are preceded by a single hyphen and may not be grouped together. Option arguments are specified in the following parameter (``-ao null``) or after a ``=`` (``-ao=null``).

- GNU style long options, like ``--colors``. GNU style long options can be more than one character long, are preceded by two hyphens, and can't be grouped together. Option arguments may be specified after a ``=`` (``--quoting-style=shell``), or, if ``--require-parameter`` is given, in the following parameter (``--quoting-style shell``).

Multiple commands and paths can be given in one call to define the same completions for multiple commands.

Multiple command switches and wrapped commands can also be given to define multiple completions in one call.

Invoking ``complete`` multiple times for the same command adds the new definitions on top of any existing completions defined for the command.

When ``-a`` or ``--arguments`` is specified in conjunction with long, short, or old style options, the specified arguments are only completed as arguments for any of the specified options. If ``-a`` or ``--arguments`` is specified without any long, short, or old style options, the specified arguments are used when completing non-option arguments to the command (except when completing an option argument that was specified with ``-r`` or ``--require-parameter``).

Command substitutions found in ``ARGUMENTS`` should return a newline-separated list of arguments, and each argument may optionally have a tab character followed by the argument description. Description given this way override a description given with ``-d`` or ``--description``.

Descriptions given with ``--description`` are also used to group options given with ``-s``, ``-o`` or ``-l``. Options with the same (non-empty) description will be listed as one candidate, and one of them will be picked. If the description is empty or no description was given this is skipped.

The ``-w`` or ``--wraps`` options causes the specified command to inherit completions from another command, "wrapping" the other command. The wrapping command can also have additional completions. A command can wrap multiple commands, and wrapping is transitive: if A wraps B, and B wraps C, then A automatically inherits all of C's completions. Wrapping can be removed using the ``-e`` or ``--erase`` options. Wrapping only works for completions specified with ``-c`` or ``--command`` and are ignored when specifying completions with ``-p`` or ``--path``.

When erasing completions, it is possible to either erase all completions for a specific command by specifying ``complete -c COMMAND -e``, or by specifying a specific completion option to delete.

When ``complete`` is called without anything that would define or erase completions (options, arguments, wrapping, ...), it shows matching completions instead. So ``complete`` without any arguments shows all loaded completions, ``complete -c foo`` shows all loaded completions for ``foo``. Since completions are :ref:`autoloaded <syntax-function-autoloading>`, you will have to trigger them first.

Examples
--------

The short style option ``-o`` for the ``gcc`` command needs a file argument:

::

    complete -c gcc -s o -r


The short style option ``-d`` for the ``grep`` command requires one of ``read``, ``skip`` or ``recurse``:

::

    complete -c grep -s d -x -a "read skip recurse"


The ``su`` command takes any username as an argument. Usernames are given as the first colon-separated field in the file /etc/passwd. This can be specified as:

::

    complete -x -c su -d "Username" -a "(cat /etc/passwd | cut -d : -f 1)"


The ``rpm`` command has several different modes. If the ``-e`` or ``--erase`` flag has been specified, ``rpm`` should delete one or more packages, in which case several switches related to deleting packages are valid, like the ``nodeps`` switch.

This can be written as:

::

    complete -c rpm -n "__fish_contains_opt -s e erase" -l nodeps -d "Don't check dependencies"


where ``__fish_contains_opt`` is a function that checks the command line buffer for the presence of a specified set of options.

To implement an alias, use the ``-w`` or ``--wraps`` option:


::

    complete -c hub -w git


Now hub inherits all of the completions from git. Note this can also be specified in a function declaration (``function thing -w otherthing``).

::

   complete -c git

Show all completions for ``git``.
docs: Add labels to all commands This allows us to use :ref: references, which don't require hardcoding it as html [ci skip] 2019-03-31 17:05:09 +08:00			`.. _cmd-complete:`

Switch command docs from \section to reStructuredText 2018-12-17 09:39:33 +08:00			`complete - edit command specific tab-completions`
Fix command section separator line lengths 2019-01-03 12:10:47 +08:00			`================================================`
Switch command docs from \section to reStructuredText 2018-12-17 09:39:33 +08:00
Migrate the 'synopsis' sections to .rst format 2018-12-18 09:58:24 +08:00			`Synopsis`
			`--------`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Commit doc_src progress. This is continuing the work I've been doing to remove the :: formatting for the synopsis sections of our manual pages. 2021-12-18 05:58:38 +08:00			``complete`` -c \| --command \| -p \| --path [options] COMMAND
complete synopsis should just be a synopsis. 2021-12-11 16:41:09 +08:00			``complete`` -C STRING \| --do-complete STRING
Migrate the 'synopsis' sections to .rst format 2018-12-18 09:58:24 +08:00
Convert \\subsection sections into rst format 2018-12-19 10:44:30 +08:00			`Description`
Fix command section separator line lengths 2019-01-03 12:10:47 +08:00			`-----------`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			``complete`` defines, removes or lists completions for a command.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			For an introduction to writing your own completions, see :ref:`Writing your own completions <completion-own>` in
			`the fish manual.`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
complete: print completions without the implied `-c` switch This switch is no longer necessary when only one command is given. Internally completions are stored separately for each command, so we only every print one command name per "complete" line anyway. 2020-10-10 17:54:52 +08:00			- ``-c COMMAND`` or ``--command COMMAND`` specifies that ``COMMAND`` is the name of the command. If there is no ``-c`` or ``-p``, one non-option argument will be used as the command.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-p COMMAND`` or ``--path COMMAND`` specifies that ``COMMAND`` is the absolute path of the command (optionally containing wildcards).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			- ``-e`` or ``--erase`` deletes the specified completion.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			- ``-s SHORT_OPTION`` or ``--short-option=SHORT_OPTION`` adds a short option to the completions list.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			- ``-l LONG_OPTION`` or ``--long-option=LONG_OPTION`` adds a GNU style long option to the completions list.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			- ``-o LONG_OPTION`` or ``--old-option=LONG_OPTION`` adds an old style long option to the completions list (See below for details).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Tweak documentation wording to include non-option arguments 2021-05-17 02:47:05 +08:00			- ``-a ARGUMENTS`` or ``--arguments=ARGUMENTS`` adds the specified option arguments to the completions list.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Tweak documentation wording to include non-option arguments 2021-05-17 02:47:05 +08:00			- ``-k`` or ``--keep-order`` keeps the order of ``ARGUMENTS`` instead of sorting alphabetically. Multiple ``complete`` calls with ``-k`` result in arguments of the later ones displayed first.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-f`` or ``--no-files`` says that this completion may not be followed by a filename.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-F`` or ``--force-files`` says that this completion may be followed by a filename, even if another applicable ``complete`` specified ``--no-files``.
complete: Add "--force-files" This allows a completion to specify that it takes files. Useful for things like `sudo -e`, because sudo usually doesn't take any files. 2019-05-31 01:12:49 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-r`` or ``--require-parameter`` says that this completion must have an option argument, i.e. may not be followed by another option.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-x`` or ``--exclusive`` is short for ``-r`` and ``-f``.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			- ``-w WRAPPED_COMMAND`` or ``--wraps=WRAPPED_COMMAND`` causes the specified command to inherit completions from the wrapped command (See below for details).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-n CONDITION`` or ``--condition CONDITION`` specifies that this completion should only be used if the CONDITION (a shell command) returns 0. This makes it possible to specify completions that should only be used in some cases.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			- ``-C STRING`` or ``--do-complete=STRING`` makes complete try to find all possible completions for the specified string. If there is no STRING, the current commandline is used instead.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			Command specific tab-completions in ``fish`` are based on the notion of options and arguments. An option is a parameter which begins with a hyphen, such as ``-h``, ``-help`` or ``--help``. Arguments are parameters that do not begin with a hyphen. Fish recognizes three styles of options, the same styles as the GNU getopt library. These styles are:
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Clarify that optional option arguments must have no separating space Unless we use "complete --require-parameter", we must say "-w32", not "-w 32", because the second "32" is a positional argument. Notably, old options do not have this behavior, which is a bit weird, see #8465 Taken from a discussion in #8459 2021-11-23 04:08:56 +08:00			- Short options, like ``-a``. Short options are a single character long, are preceded by a single hyphen and can be grouped together (like ``-la``, which is equivalent to ``-l -a``). Option arguments may be specified by appending the option with the value (``-w32``), or, if ``--require-parameter`` is given, in the following parameter (``-w 32``).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
builtin complete: document that old-style option args can be given after = Fixes #8457 2021-11-19 12:36:15 +08:00			- Old style long options, like ``-Wall`` or ``-name``. Old style long options can be more than one character long, are preceded by a single hyphen and may not be grouped together. Option arguments are specified in the following parameter (``-ao null``) or after a ``=`` (``-ao=null``).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Clarify that optional option arguments must have no separating space Unless we use "complete --require-parameter", we must say "-w32", not "-w 32", because the second "32" is a positional argument. Notably, old options do not have this behavior, which is a bit weird, see #8465 Taken from a discussion in #8459 2021-11-23 04:08:56 +08:00			- GNU style long options, like ``--colors``. GNU style long options can be more than one character long, are preceded by two hyphens, and can't be grouped together. Option arguments may be specified after a ``=`` (``--quoting-style=shell``), or, if ``--require-parameter`` is given, in the following parameter (``--quoting-style shell``).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			`Multiple commands and paths can be given in one call to define the same completions for multiple commands.`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			`Multiple command switches and wrapped commands can also be given to define multiple completions in one call.`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			Invoking ``complete`` multiple times for the same command adds the new definitions on top of any existing completions defined for the command.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Tweak documentation wording to include non-option arguments 2021-05-17 02:47:05 +08:00			When ``-a`` or ``--arguments`` is specified in conjunction with long, short, or old style options, the specified arguments are only completed as arguments for any of the specified options. If ``-a`` or ``--arguments`` is specified without any long, short, or old style options, the specified arguments are used when completing non-option arguments to the command (except when completing an option argument that was specified with ``-r`` or ``--require-parameter``).
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Tweak documentation wording to include non-option arguments 2021-05-17 02:47:05 +08:00			Command substitutions found in ``ARGUMENTS`` should return a newline-separated list of arguments, and each argument may optionally have a tab character followed by the argument description. Description given this way override a description given with ``-d`` or ``--description``.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Document how complete groups options Fixes #8146. 2021-07-24 01:29:16 +08:00			Descriptions given with ``--description`` are also used to group options given with ``-s``, ``-o`` or ``-l``. Options with the same (non-empty) description will be listed as one candidate, and one of them will be picked. If the description is empty or no description was given this is skipped.

docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			The ``-w`` or ``--wraps`` options causes the specified command to inherit completions from another command, "wrapping" the other command. The wrapping command can also have additional completions. A command can wrap multiple commands, and wrapping is transitive: if A wraps B, and B wraps C, then A automatically inherits all of C's completions. Wrapping can be removed using the ``-e`` or ``--erase`` options. Wrapping only works for completions specified with ``-c`` or ``--command`` and are ignored when specifying completions with ``-p`` or ``--path``.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			When erasing completions, it is possible to either erase all completions for a specific command by specifying ``complete -c COMMAND -e``, or by specifying a specific completion option to delete.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			When ``complete`` is called without anything that would define or erase completions (options, arguments, wrapping, ...), it shows matching completions instead. So ``complete`` without any arguments shows all loaded completions, ``complete -c foo`` shows all loaded completions for ``foo``. Since completions are :ref:`autoloaded <syntax-function-autoloading>`, you will have to trigger them first.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Let `complete` show completions for one command if just given `-c` Currently only `complete` will list completions, and it will list all of them. That's a bit ridiculous, especially since `complete -c foo` just does nothing. So just make `complete -c foo` list all the completions for `foo`. 2020-09-10 00:03:39 +08:00			`Examples`
			`--------`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			The short style option ``-o`` for the ``gcc`` command needs a file argument:
Switch \fish sections to rst format 2018-12-19 11:14:04 +08:00
			`::`

			`complete -c gcc -s o -r`

Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
docs: Improve complete docs A bit stuffy, some weird bits (I don't think GNU-style long options can typically be abbreviated, ``true --v`` and ``bash --hel`` don't work). 2020-09-10 00:56:25 +08:00			The short style option ``-d`` for the ``grep`` command requires one of ``read``, ``skip`` or ``recurse``:
Switch \fish sections to rst format 2018-12-19 11:14:04 +08:00
			`::`

			`complete -c grep -s d -x -a "read skip recurse"`

Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			The ``su`` command takes any username as an argument. Usernames are given as the first colon-separated field in the file /etc/passwd. This can be specified as:
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch \fish sections to rst format 2018-12-19 11:14:04 +08:00			`::`

			`complete -x -c su -d "Username" -a "(cat /etc/passwd \| cut -d : -f 1)"`

Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			The ``rpm`` command has several different modes. If the ``-e`` or ``--erase`` flag has been specified, ``rpm`` should delete one or more packages, in which case several switches related to deleting packages are valid, like the ``nodeps`` switch.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
			`This can be written as:`

Switch \fish sections to rst format 2018-12-19 11:14:04 +08:00			`::`

			`complete -c rpm -n "__fish_contains_opt -s e erase" -l nodeps -d "Don't check dependencies"`

Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			where ``__fish_contains_opt`` is a function that checks the command line buffer for the presence of a specified set of options.
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch backticks to double backticks for rst compatibility 2018-12-20 04:02:45 +08:00			To implement an alias, use the ``-w`` or ``--wraps`` option:
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Switch \fish sections to rst format 2018-12-19 11:14:04 +08:00

			`::`

			`complete -c hub -w git`

Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Let `complete` show completions for one command if just given `-c` Currently only `complete` will list completions, and it will list all of them. That's a bit ridiculous, especially since `complete -c foo` just does nothing. So just make `complete -c foo` list all the completions for `foo`. 2020-09-10 00:03:39 +08:00			Now hub inherits all of the completions from git. Note this can also be specified in a function declaration (``function thing -w otherthing``).

			`::`
docs: Fix markup for code blocks 2020-10-11 03:22:34 +08:00
Let `complete` show completions for one command if just given `-c` Currently only `complete` will list completions, and it will list all of them. That's a bit ridiculous, especially since `complete -c foo` just does nothing. So just make `complete -c foo` list all the completions for `foo`. 2020-09-10 00:03:39 +08:00			`complete -c git`
Copy doc_src to sphinx_doc_src and add a TOC 2018-12-17 05:08:41 +08:00
Let `complete` show completions for one command if just given `-c` Currently only `complete` will list completions, and it will list all of them. That's a bit ridiculous, especially since `complete -c foo` just does nothing. So just make `complete -c foo` list all the completions for `foo`. 2020-09-10 00:03:39 +08:00			Show all completions for ``git``.