Re: Actual use cases for non-filename behaviour of glob?

> non-filename behaviour of glob

That's probably a misunderstanding, it's directly related to the behaviour of file-globs in Unix shells

Try something like ls *.{txt,bak} to see what I mean. (untested b/c on Win)

I used it sometimes in production code, and we already had several questions asking for easy permutation syntax.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

Comment on Re: Actual use cases for non-filename behaviour of glob? Download Code

Replies are listed 'Best First'.
Re^2: Actual use cases for non-filename behaviour of glob? by vrk (Chaplain) on Apr 10, 2017 at 14:52 UTC
I'm not sure where the misunderstanding is. I often use the set (brace) notation in bash, e.g. when temporarily renaming files (`mv file.name{,.old}`). The question isn't about the glob syntax -- it's about being able to produce strings from a glob call that have nothing to do with files in the current directory.	[reply] [d/l]
Re^3: Actual use cases for non-filename behaviour of glob? by LanX (Saint) on Apr 10, 2017 at 17:07 UTC
> I'm not sure where the misunderstanding is. Probably on my side? ;) I use it for quick fixes, like at the moment for limiting a tree to certain IDs for testing. (jQuery EasyUI TreeGrid needs unique IDs per node, I use something like 1_2_3_4 and I don't wanna wait and click thru the whole tree while testing in the browser) Another example out of many Re: Substitution of a particular letter in all combinations of positions in word (see inside). but I agree that it's rather on the one-liner/write-once edge of the spectre. (Due to the limitation to strings and the special syntax) Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]