[Coco] Shell+ 2.2a manual and wildcards

[L. Curtis Boyle]

If the command supports multiple filenames at once, then wildcards should work (not all do). By default, you have to put a colon as the first character of a line for wildcarding in Shellplus 2.2a. Also, a note: some commands have their own built in wildcard handling, and having Shell attempt to do its own wildcarding at the same time screws that up, which is why it was defaulted go off in 2.2a. (While Shell’s wildcarding is quite nice (one of the few to add ranged character searches - [a-f] range, for example - it is also limited by a maximum 2k buffer to pass as a parameter. So in large directories with a lot of matches, it will error out with “expanded line too long”. Other commands (like MSCOPY) do one wildcard matching file at a time, so they will work on any size directory. 

Sent from my iPhone

> On Mar 28, 2019, at 1:22 AM, Walter Zambotti <zambotti at iinet.net.au> wrote:
> 
> I found the 2.1 manual in the archive.
> 
> 
> 
> Is there a 2.2a manual or a list of changes somewhere.
> 
> 
> 
> I can't seem to get wildcards working at all.
> 
> 
> 
> I would expect the following command:
> 
> 
> 
> $ echo *
> 
> *
> 
> 
> 
> To echo every file name in the directory or
> 
> 
> 
> $ list *
> 
> ERROR #215
> 
> 
> 
> To list every filename in the directory.
> 
> 
> 
> Walter
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>