git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Some sub-commands can't be completed by TAB key.

From
Johannes Sixt <j6t@kdbg.org>
Date
Jan 22, 2022, 14:47 UTC
Message-ID
<5373af01-eeae-fb66-e9f7-41f2a022b275@kdbg.org>
In-Reply-To
<CAGP6POJ9gwp+t-eP3TPkivBLLbNb2+qj=61Mehcj=1BgrVOSLA@mail.gmail.com>
Am 22.01.22 um 09:42 schrieb Hongyi Zhao:
Show 12 quoted lines
> I find that there are some  sub-commands can't be completed by TAB key:
> 
> $ git <TAB>
> add               cherry-pick       fetch             latexdiff
> [...]
> As you can see, there are some sub-commands which are not listed in
> the above list, for example, the following ones:
> 
> $ git ls-remote
> $ git ls-files
> 
> Any hints for this problem?

Tab completion is only available for user-facing sub-commands ("porcelain"), but not for sub-commands intended for scripting ("plumbing"). The intent is to make tab completion more efficient during day-to-day work on the command line. For example,

   $ git l<TAB>
arrives at
   $ git log <cursor here>
instead of
   log     ls-files     ls-remote     ls-tree
   $ git l<cursor here>
-- Hannes
Previous: Hongyi ZhaoNext: Hongyi Zhao
Message 2 of 17 in “Some sub-commands can't be completed by TAB key.”
  1. Hongyi ZhaoJan 22, 2022
  2. Johannes SixtJan 22, 2022
  3. Hongyi ZhaoJan 23, 2022
  4. Philippe BlainJan 23, 2022
  5. Junio C HamanoJan 23, 2022
  6. Hongyi ZhaoJan 24, 2022
  7. João Victor BonfimJan 24, 2022
  8. Junio C HamanoJan 25, 2022
  9. completion: add a GIT_COMPLETION_SHOW_ALL_COMMANDSÆvar Arnfjörð Bjarmason, Jan 25, 2022
  10. Junio C HamanoJan 26, 2022
  11. 0/2 completion: add a GIT_COMPLETION_SHOW_ALL_COMMANDSÆvar Arnfjörð Bjarmason, Feb 2, 2022
  12. 1/2 completion tests: re-source git-completion.bash in a subshellÆvar Arnfjörð Bjarmason, Feb 2, 2022
  13. 2/2 completion: add a GIT_COMPLETION_SHOW_ALL_COMMANDSÆvar Arnfjörð Bjarmason, Feb 2, 2022
  14. SZEDER GáborFeb 6, 2022
  15. Junio C HamanoFeb 6, 2022
  16. SZEDER GáborFeb 6, 2022
  17. Junio C HamanoFeb 7, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.