command <someCommand>
missing in several places throughout the shell code
#3458
Closed
5 of 10 tasks
man fzf
)Info
Problem / Steps to reproduce
Hey.
AFAIU, you use
command <someCommand>
in the sourced shell files to prevent undesired alias subsitution, which would likely break everything - just as e.g. bash-completion does as well and which of course is a good thing.Looking at the shell code (
completion.bash
andkey-bindings.bash
at least), there are however numerous places where this isn't done, e.g.:fzf/shell/completion.bash
Line 17 in a3ff49a
fzf/shell/completion.bash
Line 51 in a3ff49a
fzf/shell/completion.bash
Line 175 in a3ff49a
fzf/shell/completion.bash
Lines 284 to 287 in a3ff49a
I could try to write a patch that adds
command
, but:command
I think for cases like
awk
ortr
it makes sense to usecommand
. I also have seen cases, where people aliasecho
/printf
. Not sure about things likeread
,break
oreval
. I'd tend to perhaps usecommand
forread
but not for any of the special built-ins.Also, function names like in:
fzf/shell/completion.bash
Line 185 in a3ff49a
may be aliased, too.
We could in principle avoid alias substitution in such cases by quoting the function name, not sure whether this should be done though.
Cheers,
Chris.
The text was updated successfully, but these errors were encountered: