From: Junio C Hamano <hidden> Date: 2022-01-23 19:51:57
Philippe Blain [off-list ref] writes:
quoted
I see the following:
$ git l<TAB>
latexdiff log
This would mean you have a 'git-latexdiff' command somewhere in your PATH.
True. On Debian-based systems, the texlive-extra-utils package has
/usr/bin/git-latexdiff and that is likely where it came from.
It is also worth noting that completion will also include whatever
alias. I get "lg" in the mix because I have
[alias]
lg = "log --oneline"
in my $HOME/.gitconfig, for example.
On Mon, Jan 24, 2022 at 3:51 AM Junio C Hamano [off-list ref] wrote:
Philippe Blain [off-list ref] writes:
quoted
quoted
I see the following:
$ git l<TAB>
latexdiff log
This would mean you have a 'git-latexdiff' command somewhere in your PATH.
True. On Debian-based systems, the texlive-extra-utils package has
/usr/bin/git-latexdiff and that is likely where it came from.
Mine comes from TexLive:
$ which git-latexdiff
/opt/texlive/2021/bin/x86_64-linux/git-latexdiff
It is also worth noting that completion will also include whatever
alias. I get "lg" in the mix because I have
[alias]
lg = "log --oneline"
in my $HOME/.gitconfig, for example.
From: Junio C Hamano <hidden> Date: 2022-01-25 07:36:08
João Victor Bonfim [off-list ref]
writes:
quoted
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.