Re: [PATCH 7/8] ls-files: support --max-depth

3 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH 7/8] ls-files: support --max-depth

From: Matthieu Moy <hidden>
Date: 2016-06-15 23:00:34

Duy Nguyen [off-list ref] writes:
I'd rather go with no trailing slash by default and add -F (which
seems to be more than just '/')
... and then add a configuration variable to let users enable it by
default.

For GNU ls, I have "alias ls='ls -F --color=auto'" in my shell's
configuration, but I cannot push the analogy by aliasing "git ls"
because Git doesn't allow aliasing existing commands.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: [PATCH 7/8] ls-files: support --max-depth

From: Duy Nguyen <hidden>
Date: 2016-06-15 23:00:34

On Fri, Mar 28, 2014 at 8:52 PM, Matthieu Moy
[off-list ref] wrote:
Duy Nguyen [off-list ref] writes:
quoted
I'd rather go with no trailing slash by default and add -F (which
seems to be more than just '/')
... and then add a configuration variable to let users enable it by
default.

For GNU ls, I have "alias ls='ls -F --color=auto'" in my shell's
configuration, but I cannot push the analogy by aliasing "git ls"
because Git doesn't allow aliasing existing commands.
I can do that but I want to push for a general solution instead
of ls-only. How about config key defaults.<cmd>, containing a list of
arguments, that will be prepended to git-<cmd>? Only some commands are
marked to support this by adding USE_DEFAULTS in the array commands[]
in git.c. And "git --no-defaults <cmd>" will ignore defaults.<cmd> (or
"git -c defaults.<cmd>= <cmd>" but it's less obvious). GIT_NO_DEFAULTS
can also be set, which has the same effect for all commands.
-- 
Duy

Re: [PATCH 7/8] ls-files: support --max-depth

From: Duy Nguyen <hidden>
Date: 2016-06-15 23:00:34

On Fri, Mar 28, 2014 at 9:15 PM, Duy Nguyen [off-list ref] wrote:
On Fri, Mar 28, 2014 at 8:52 PM, Matthieu Moy
[off-list ref] wrote:
quoted
Duy Nguyen [off-list ref] writes:
quoted
I'd rather go with no trailing slash by default and add -F (which
seems to be more than just '/')
... and then add a configuration variable to let users enable it by
default.

For GNU ls, I have "alias ls='ls -F --color=auto'" in my shell's
configuration, but I cannot push the analogy by aliasing "git ls"
because Git doesn't allow aliasing existing commands.
I can do that but I want to push for a general solution instead
of ls-only. How about config key defaults.<cmd>, containing a list of
arguments, that will be prepended to git-<cmd>? Only some commands are
marked to support this by adding USE_DEFAULTS in the array commands[]
in git.c. And "git --no-defaults <cmd>" will ignore defaults.<cmd> (or
"git -c defaults.<cmd>= <cmd>" but it's less obvious). GIT_NO_DEFAULTS
can also be set, which has the same effect for all commands.
Another option is to make git recognize program name g<something> and
auto map it to the alias <something>. For example, the symlink "gls"
will be executed as "git ls" (and the alias version is preferred over
the builtin one). Of course you can't have alias "it" because "git" is
already taken. It works for many cases, it's faster to type, and it
does not break current scripts.
-- 
Duy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help