On 7/1/20 4:50 PM, Chet Ramey wrote:
>> But implementing it seems tricky: ${x;%} reliably errors whether or not x is
>> set, ${x~#%} never does (I can't find what ~ is supposed to do here in the
>> man
>> page,
>
> Of course the first one errors -- `x;' is not a valid parameter name (and
> we won't even talk about the missing pattern after `%'). I don't think
> there's any argument there.
>
> The second case is clearly a bug. It should produce an error.
My fault. I thought I had disabled that feature, but it's still in there.
It's one of the case-changing operators (the undocumented case-toggling
one). It's not particularly useful.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
_______________________________________________
Toybox mailing list
Toybox@lists.landley.net
http://lists.landley.net/listinfo.cgi/toybox-landley.net
