Difference between revisions of "bash/globbing"

from HTYP, the free directory anyone can edit if they can prove to me that they're not a spambot
Jump to navigation Jump to search
(problem, workarounds, TC post)
Line 21: Line 21:
 
* {{l/manpage|glob}}
 
* {{l/manpage|glob}}
 
* {{wikipedia|glob (programming)}}
 
* {{wikipedia|glob (programming)}}
 +
* [https://mywiki.wooledge.org/glob Greg's Wiki]
 
* [https://www.php.net/manual/en/function.glob.php PHP: glob]
 
* [https://www.php.net/manual/en/function.glob.php PHP: glob]
 
* '''2020-02-04''' [https://toot.cat/@woozle/103603799224715530 Linux hot take: bash bashing]
 
* '''2020-02-04''' [https://toot.cat/@woozle/103603799224715530 Linux hot take: bash bashing]

Revision as of 13:57, 9 February 2020

The following notes may apply to other shell environments besides bash, but have only been tested with bash.

Commands invoked via bash always, by default, have each of their arguments parsed via the glob system facility before being passed to the command.

Problem

This actively interferes with the ability of programs such as grep to behave intuitively when given a file-mask spec as input for processing, because:

  • any mask entered will apply only to the current folder.
  • folders are only included if their names also match the mask
    • ...thus not being useful as far as being the next layer of folders to search; the program will have to get its own directory listing for that.

Workarounds

Globbing can be turned off on a per-session basis:

  • set -o noglob
    turns off globbing
    put it in ~/.bashrc to make it the default
  • set +o noglob
    turns globbing back on
  • help set
    returns more information about bash's set command (the "set" manpage is for something else)

The user can bypass globbing (and other special-character processing) by enclosing the file-mask in quotes (single or double). bash will strip off the quotes but not parse the contents.

Links