Date: Thu, 26 Apr 2018 12:09:15 +0100
From: Geoff Clare <g...@opengroup.org>
Message-ID: <20180426110915.GB24507@lt2.masqnet>
| What we're discussing here
| is allowing the expansion of .* not to include them when they do exist.
Personally I don't mind that ".*" includes (or might include) "." - that's
trivial to avoid, ".?*" matches the exact same thing as ".*" except when
the "*" in the latter matches nothing, ie: "." - and leaving the '.' case
there has a kind of elegance.
But ".." is more painful, .[!.]* doesn't work, as it also blocks ..x (etc).
Getting rid of that would be useful, and almost never a problem,
scripts that want to go up the tree (intentionally) generally do it
explicitly, not just as a side effect of "* .*" (and then dealing with
the consequences of each of those potentially matching nothing
and remaining literal - including dealing with the sole file name
matched being literally '*' (or '.*') ... an option to make "no matches"
produce the empty string would often be useful.)
kre
