Well, how should I accomplish what I’ve been trying to do with ‘*’ ? On Mon, Aug 31, 2020 at 14:38 Kurtis Rader <kra...@skepticism.us> wrote:
> On Mon, Aug 31, 2020 at 11:13 AM John Chludzinski < > john.chludzin...@gmail.com> wrote: > >> Whereas, I’ve haven’t had time to try again to duplicate the ‘rm’ >> problem, I have encountered yet another * “issue”: >> >> I tried: >> >> ls >> ./a10_soc_devkit_ghrd/software/bootloader/u-boot-socfpga/arch/arm/dts/'*10*' >> > > That won't work because quoting the wildcard causes the shell to treat it > like any other character; i.e., it loses its meaning as a wildcard. And the > ls command does not do wildcard expansion. > > >> ls './a10_soc_devkit_ghrd/software/bootloader/u-boot- >> socfpga/arch/arm/dts/*10*' >> > > See http://fishshell.com/docs/current/index.html#wildcards. Specifically > this paragraph: > > Note that for most commands, if any wildcard fails to expand, the command >> is not executed, $status >> <http://fishshell.com/docs/current/index.html#variables-status> is set >> to nonzero, and a warning is printed. This behavior is consistent with >> setting shopt -s failglob in bash. There are exactly 4 exceptions, >> namely set <http://fishshell.com/docs/current/cmds/set.html#cmd-set>, >> overriding variables in overrides >> <http://fishshell.com/docs/current/index.html#variables-override>, count >> <http://fishshell.com/docs/current/cmds/count.html#cmd-count> and for >> <http://fishshell.com/docs/current/cmds/for.html#cmd-for>. Their globs >> are permitted to expand to zero arguments, as with shopt -s nullglob in >> bash. > > > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank > > >
_______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
