Nevermind! I was misunderstanding what the 'command' builtin does! Thank you, Carl
> On 5/17/2021 3:40 PM Carl Thompson <c...@carlthompson.net> wrote: > > > > Configuration Information [Automatically generated, do not change]: > Machine: x86_64 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt > -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' > -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash.b > ashrc' -DSYS_BASH_LOGOUT='/etc/bash.bash_logout' > -DNON_INTERACTIVE_LOGIN_SHELLS > uname output: Linux clip 5.10.26-brunch-sebanc #1 SMP PREEMPT Wed Apr 7 > 21:32:32 CEST 2021 x86_64 GNU/Linux > Machine Type: x86_64-pc-linux-gnu > > Bash Version: 5.1 > Patch Level: 4 > Release Status: release > > Description: > 'command' builtin doesn't seem to work for external 'printf'. It > appears to use the builtin. > > --------------------------------------------------- > [cet@clip ~]$ printf > printf: usage: printf [-v var] format [arguments] > > [cet@clip ~]$ type -P printf > /usr/bin/printf > > [cet@clip ~]$ /usr/bin/printf > /usr/bin/printf: missing operand > Try '/usr/bin/printf --help' for more information. > > [cet@clip ~]$ command printf > printf: usage: printf [-v var] format [arguments] > --------------------------------------------------- > > I believe that running 'command printf' should yield the same result > as running '/usr/bin/printf' > > Repeat-By: > (See above) >
