On Mon, Oct 10, 2022 at 9:08 PM Chet Ramey <chet.ra...@case.edu> wrote:
> That's not the point. The point is that shell pattern matching is used in
> contexts other than filename globbing, and the shell shouldn't broadly
> impose a filename-only restriction on those uses.
>
> Chet
>
Ok got it, I was confused because the manual occurences of the term GLOB in
bash doc seems to appears only in the "Pathname Expansion" paragraph,
which point to a sub-paragraph called "Pattern Matching" so it looked to
me like if "Pattern Matching" applied to "Pathname Expansion"
Inside "Pattern Matching" we see ref to things like
glob-complete-word (glob-* :-) ) all apply to
"pattern for pathname expansion"
extglob If set, the extended pattern matching features described
above under Pathname Expansion are enabled.
nocaseglob
If set, bash matches filename...
So at the point I thought that globbing was kind of related to the max file
path of an OS.
On the contrary I see nor reference saying the 'pattern matching for
pathname expansion can also be used by extension to any strings, but now I
understand it is.
Yet let me know the strategy or limit you choose, and I will do the same
for ksh93
Cheers,
