🚀 go-pugleaf

I set up a decompress program reference object and associated it with
"*.z"; it is supposed to feed data objects that end this way to
"decompress -d". It works as advertised _as long as there is no more
than one period in the filename._ That is, filenames seem to be parsed
from the left, so that abc.z gets decompressed when I double-click on
it, but abc.def.z (a legitimate compressed version of abc.def) doesn't
match. This seems to be a mismatch between the WPS and cmd.exe (and
4os2), since the command processor(s) recognize abc.def.z as matching
*.z, but the WPS program objects doesn't.

Okay, I sez, I'll redefine the template as "*z". This works, except that
it matches too much. In particular, I'd like to match a "gzip -d"
program reference object to anything ending in ".gz" and "compress -d"
to anything ending in ".z". I can wiggle around this by associating gzip
first to "*gz" and then compress to "*z"; the first association becomes
the default, so everything will work (gzipped files get associated with
both ungzip and uncompress, but the former is the default, while
compressed files are associated only with uncompress). But this isn't
the way nature (or, I hope, IBM, intended); I would expect the WPS to
expand wildcards the same way as the command processor, so that I
should be able to specify "*.z" and match both "abc.z" and
"abc.def.z".

Is this a design flaw? User error? Something else?

Thanks,

David
--
Professor David J. Birnbaum         djbpitt+@pitt.edu 
The Royal York Apartments, #802
3955 Bigelow Boulevard              voice: 1-412-687-4653
Pittsburgh, PA  15213  USA          fax:   1-412-624-9714