All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "João Victor Bonfim" <JoaoVictorBonfim+Git-Mail-List@protonmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Some sub-commands can't be completed by TAB key.
Date: Mon, 24 Jan 2022 23:33:25 -0800	[thread overview]
Message-ID: <xmqq1r0w1d8a.fsf@gitster.g> (raw)
In-Reply-To: Odvn8_XIojrgpHG7xMtrBXdhoxr20X_fFRYoDtvkUKb1FOd-13j_l40TBAc1hn7rSddJ-YrQak8AuetNQ9LkeVeVoS3RTlIeSQ9znqyMApc=@protonmail.com

João Victor Bonfim  <JoaoVictorBonfim+Git-Mail-List@protonmail.com>
writes:

>> It is also worth noting that completion will also include whatever
>> alias.  I get "lg" in the mix because I have...
>
> That sounds like something that should be hidden, no?
> Like, all aliases are left unmentioned?

Unlike the plumbing commands that are meant to be used in writing
scripts and not typed in interactive sessions, and more like
Porcelain commands that are meant to be used by human end-users in
their interactive sessions by getting typed from the keyboard, an
aliase is often (and certainly my "lg" is) defined in order to give
a short-and-sweet typesaver to a command with common initial options
that the user finds useful in their interactive sessions.

I am curious to find out what makes you think it is a good idea to
omit them from completion.



  reply	other threads:[~2022-01-25  7:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22  8:42 Some sub-commands can't be completed by TAB key Hongyi Zhao
2022-01-22 14:47 ` Johannes Sixt
2022-01-23  0:38   ` Hongyi Zhao
2022-01-23 17:31     ` Philippe Blain
2022-01-23 19:51       ` Junio C Hamano
2022-01-24  1:42         ` Hongyi Zhao
2022-01-24  9:18         ` João Victor Bonfim
2022-01-25  7:33           ` Junio C Hamano [this message]
2022-01-25 12:49 ` [PATCH] completion: add a GIT_COMPLETION_SHOW_ALL_COMMANDS Ævar Arnfjörð Bjarmason
2022-01-26 22:34   ` Junio C Hamano
2022-02-02 11:15   ` [PATCH v2 0/2] " Ævar Arnfjörð Bjarmason
2022-02-02 11:15     ` [PATCH v2 1/2] completion tests: re-source git-completion.bash in a subshell Ævar Arnfjörð Bjarmason
2022-02-02 11:15     ` [PATCH v2 2/2] completion: add a GIT_COMPLETION_SHOW_ALL_COMMANDS Ævar Arnfjörð Bjarmason
2022-02-06 13:30       ` SZEDER Gábor
2022-02-06 20:09         ` Junio C Hamano
2022-02-06 22:47           ` SZEDER Gábor
2022-02-07  7:03             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq1r0w1d8a.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=JoaoVictorBonfim+Git-Mail-List@protonmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.