Re: Ada.Command_Line and wildcards

[Markus E Leypold <development-2006-8ecbb5cc8aREMOVETHIS@ANDTHATm-e-leypold.de>]

Brian May <bam@snoopy.apana.org.au> writes:

>>>>>> "Georg" == Georg Bauhaus <bauhaus@futureapps.de> writes:
>
>     Georg> $ echo *.ads
>
> Get a real shell !
>
> I get:
>
> zsh: no matches found: *.ads

You get the same with bash and most bourne shells if you set the
appropriate flags here. Instead of answering to any (IMHO) mistaken
contribution in this thread here, I was planning to write a little
essay "And Unix does it bloody right after all!" (in which I correct
all those misconception, write useful things about Unix shell usage
and philosophy and post a link here). Alas -- it will not be done
soon, as I can already see: I got bogged down in other things.

Basically we're back to the old bone of contention (I think we had
that at least another time recently about FPLs) between me an Georg:
Can a user be bothered to know his/her tools or is the answer (he,
Georg, too often gets) to RTM just bloody cheek?

I think that cannot be answered finally, but I certainly prefer to
have a powerful tool and read the manual and usually I prefer to work
with users that can need not be babied through everything and after
years of using a "GUI" still do not know about a hierarchical
filesystem (not even about the concept, not about the name) and are
still absolutely confused about all the things they see on windows
explorer. makes finding anything again a bit difficult for them if the
"default" directory of an application changed ...

Regards -- Markus


> which forces you to quote the value if thats what you really wanted:
>
>> echo "*.ads"
> *.ads
>
> or set NULLGLOB:
>
>> setopt NULLGLOB
>> echo *.ads
>
> which expands *.ads into nothing.
> -- 
> Brian May <bam@snoopy.apana.org.au>