bash/globbing - Revision history

Woozle at 18:57, 23 October 2024

2024-10-23T18:57:36Z

← Older revision		Revision as of 18:57, 23 October 2024
Line 12:		Line 12:
	** a file-utility might want a glob to refer to the names of files being acted on, as a means of defining the output name		** a file-utility might want a glob to refer to the names of files being acted on, as a means of defining the output name
	*** Examples:		*** Examples:
	**** <syntaxhighlight inline>copy .png .backup.*</syntaxhighlight> could mean "copy all .PNG files to this same folder but add ".backup" before the ".png"		**** <syntaxhighlight inline lang="Bash">copy .png .backup.*</syntaxhighlight> could mean "copy all .PNG files to this same folder but add ".backup" before the ".png"
	***** NOTE: DOS utilities often made use of this convention.		***** NOTE: DOS utilities often made use of this convention.
	**** <syntaxhighlight inline>move ????????.png ????/.</syntaxhighlight>" could mean, where the files all begin with a YYYYMMDD date, "move all of these files into a folder whose name is the year given in the filename"		**** <syntaxhighlight inline lang="Bash">move ????????.png ????/.</syntaxhighlight>" could mean, where the files all begin with a YYYYMMDD date, "move all of these files into a folder whose name is the year given in the filename"

	===inconsistency===		===inconsistency===
Line 30:		Line 30:
	* <code>help set</code>		* <code>help set</code>
	*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)		*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)
	* Explicitly enclosing the filemask in quotes (double or single) suppresses auto-globbing. <code>bash</code> will strip off the quotes but not parse the contents.
	** The same is true for backslash-escaping the "" character, as in <code>\.log</code>		Explicitly enclosing the filemask in quotes (double or single) suppresses auto-globbing. <code>bash</code> will strip off the quotes but not parse the contents.
			* The same is true for backslash-escaping the "" character, as in <code>\.log</code>

			Untested:
			* <syntaxhighlight inline lang="Bash">ls -1 \| grep </syntaxhighlight>{{arg\|glob expression}}<syntaxhighlight inline lang="Bash"> \| xargs rm </syntaxhighlight>

	==Related==		==Related==

Woozle: /* wildcard obfuscation */

2024-10-23T18:49:39Z

wildcard obfuscation

← Older revision		Revision as of 18:49, 23 October 2024
Line 5:		Line 5:
	This actively interferes with the ability of programs such as [[grep/file masks\|grep]] to behave intuitively when given a file-mask spec as input for processing, because:		This actively interferes with the ability of programs such as [[grep/file masks\|grep]] to behave intuitively when given a file-mask spec as input for processing, because:
	===wildcard obfuscation===		===wildcard obfuscation===
	* any mask entered will apply only to the current folder.		* any mask entered will apply only to the current folder -- not subfolders or anything under them.
	* folders are only included if their names ''also'' match the mask		* folders (within the current folder) 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.		** ...thus not being useful as far as filtering recursively; the program will have to get its own directory listings for that.
	* applications are actively prevented from using wildcards in other ways that might be more intuitive in context, e.g.		* applications are actively prevented from using wildcards in other ways that might be more intuitive in context, e.g.
	** a package-manager might allow you to list (or act on) packages whose names match a glob		** a package-manager might allow you to list (or act on) packages whose names match a glob
	** a file-utility might want a glob to refer to the names of files being acted on, as a means of defining the output name		** a file-utility might want a glob to refer to the names of files being acted on, as a means of defining the output name
	*** Examples:		*** Examples:
	**** "<syntaxhighlight inline ~~lang=sh~~>copy .png .backup.*</syntaxhighlight>" could mean "copy all .PNG files to this same folder but add ".backup" before the ".png"		**** <syntaxhighlight inline>copy .png .backup.*</syntaxhighlight> could mean "copy all .PNG files to this same folder but add ".backup" before the ".png"
	***** NOTE: DOS utilities often made use of this convention.		***** NOTE: DOS utilities often made use of this convention.
			**** <syntaxhighlight inline>move ????????.png ????/.</syntaxhighlight>" could mean, where the files all begin with a YYYYMMDD date, "move all of these files into a folder whose name is the year given in the filename"

	===inconsistency===		===inconsistency===
	Apparently the file-mask will be passed literally ''if'' no matches are found. (I guess this is useful so the program can say "no matches found for {{arg\|filemask}}", but...)		Apparently the file-mask will be passed literally ''if'' no matches are found. (I guess this is useful so the program can say "no matches found for {{arg\|filemask}}", but...)

Woozle: /* Problems */

2024-10-23T16:19:10Z

Problems

← Older revision		Revision as of 16:19, 23 October 2024
Line 8:		Line 8:
	* folders are only included if their names ''also'' match the mask		* 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.		** ...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.
			* applications are actively prevented from using wildcards in other ways that might be more intuitive in context, e.g.
			** a package-manager might allow you to list (or act on) packages whose names match a glob
			** a file-utility might want a glob to refer to the names of files being acted on, as a means of defining the output name
			*** Examples:
			**** "<syntaxhighlight inline lang=sh>copy .png .backup.*</syntaxhighlight>" could mean "copy all .PNG files to this same folder but add ".backup" before the ".png"
			***** NOTE: DOS utilities often made use of this convention.
	===inconsistency===		===inconsistency===
	Apparently the file-mask will be passed literally ''if'' no matches are found. (I guess this is useful so the program can say "no matches found for {{arg\|filemask}}", but...)		Apparently the file-mask will be passed literally ''if'' no matches are found. (I guess this is useful so the program can say "no matches found for {{arg\|filemask}}", but...)
	===ambiguity===		===ambiguity===
	If there is a file whose name looks like an option because it begins with "-" or "--", and that file matches the file-mask given, the auto-globbing feature will include it verbatim in such a way that the executable may not be able to tell whether it's part of a file-listing or is actually an option from the command-line.		If there is a file whose name looks like an option because it begins with "-" or "--", and that file matches the file-mask given, the auto-globbing feature will include it verbatim in such a way that the executable may not be able to tell whether it's part of a file-listing or is actually an option from the command-line.

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

Woozle: /* Related */

2022-09-03T23:51:22Z

← Older revision		Revision as of 23:51, 3 September 2022
Line 26:		Line 26:
	==Related==		==Related==
	* [[grep/file masks]]		* [[grep/file masks]]
			* [[PHP/file/glob]]: globbing functions in PHP

	==Links==		==Links==
	* {{l/manpage\|glob}}		* {{l/manpage\|glob}}

Woozle: /* Workarounds */

2022-06-18T01:05:48Z

Workarounds

← Older revision		Revision as of 01:05, 18 June 2022
Line 22:		Line 22:
	*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)		*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)
	* Explicitly enclosing the filemask in quotes (double or single) suppresses auto-globbing. <code>bash</code> will strip off the quotes but not parse the contents.		* Explicitly enclosing the filemask in quotes (double or single) suppresses auto-globbing. <code>bash</code> will strip off the quotes but not parse the contents.
			** The same is true for backslash-escaping the "" character, as in <code>\.log</code>

	==Related==		==Related==
	* [[grep/file masks]]		* [[grep/file masks]]

Woozle at 01:01, 18 June 2022

2022-06-18T01:01:10Z

← Older revision		Revision as of 01:01, 18 June 2022
Line 2:		Line 2:

	Commands invoked via bash always, by default, have each of their arguments parsed via the [[glob]] system facility before being passed to the command.		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~~==		==Problems==
	This actively interferes with the ability of programs such as [[grep/file masks\|grep]] to behave intuitively when given a file-mask spec as input for processing, because:		This actively interferes with the ability of programs such as [[grep/file masks\|grep]] to behave intuitively when given a file-mask spec as input for processing, because:
			===wildcard obfuscation===
	* any mask entered will apply only to the current folder.		* any mask entered will apply only to the current folder.
	* folders are only included if their names ''also'' match the mask		* 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.		** ...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===		===inconsistency===
			Apparently the file-mask will be passed literally ''if'' no matches are found. (I guess this is useful so the program can say "no matches found for {{arg\|filemask}}", but...)
			===ambiguity===
			If there is a file whose name looks like an option because it begins with "-" or "--", and that file matches the file-mask given, the auto-globbing feature will include it verbatim in such a way that the executable may not be able to tell whether it's part of a file-listing or is actually an option from the command-line.
			==Workarounds==
	Globbing can be turned off on a per-session basis:		Globbing can be turned off on a per-session basis:
	* <code>set -o noglob</code>		* <code>set -o noglob</code>
Line 16:		Line 21:
	* <code>help set</code>		* <code>help set</code>
	*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)		*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)
			* Explicitly enclosing the filemask in quotes (double or single) suppresses auto-globbing. <code>bash</code> will strip off the quotes but not parse the contents.
	~~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.		==Related==
			* [[grep/file masks]]
	==Links==		==Links==
	* {{l/manpage\|glob}}		* {{l/manpage\|glob}}

Woozle: /* Links */

2020-02-09T13:57:04Z

Links

← Older revision		Revision as of 13:57, 9 February 2020
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]

Woozle: problem, workarounds, TC post

2020-02-05T18:44:49Z

problem, workarounds, TC post

← Older revision		Revision as of 18:44, 5 February 2020
Line 2:		Line 2:

	Commands invoked via bash always, by default, have each of their arguments parsed via the [[glob]] system facility before being passed to the command.		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/file masks\|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:		Globbing can be turned off on a per-session basis:
	* <code>set -o noglob</code>		* <code>set -o noglob</code>
Line 11:		Line 16:
	* <code>help set</code>		* <code>help set</code>
	*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)		*: returns more information about bash's <code>set</code> 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==		==Links==
	* {{l/manpage\|glob}}		* {{l/manpage\|glob}}
	* {{wikipedia\|glob (programming)}}		* {{wikipedia\|glob (programming)}}
	* [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]

Woozle: Created page with "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 o..."

2020-02-05T18:20:09Z

Created page with "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 o..."

New page

The following notes may apply to other [[shell environment]]s 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.

Globbing can be turned off on a per-session basis:
* <code>set -o noglob</code>
*:turns off globbing
*: put it in <code>~/.bashrc</code> to make it the default
* <code>set +o noglob</code>
*: turns globbing back on
* <code>help set</code>
*: returns more information about bash's <code>set</code> command (the "set" manpage is for something else)
==Links==
* {{l/manpage|glob}}
* {{wikipedia|glob (programming)}}
* [https://www.php.net/manual/en/function.glob.php PHP: glob]