Path: utzoo!attcan!uunet!husc6!spdcc!merk!alliant!rosenkra
From: rosenkra@Alliant.COM (Bill Rosenkranz)
Newsgroups: comp.sys.atari.st
Subject: Re: More Gulam problems
Message-ID: <2137@alliant.Alliant.COM>
Date: 20 Jul 88 21:34:35 GMT
References: <19880719193319.2.JRD@MOA.SCRC.Symbolics.COM>
Reply-To: rosenkra@alliant.UUCP (Bill Rosenkranz)
Organization: Alliant Computer Systems, Littleton, MA
Lines: 29

---
In article <19880719193319.2.JRD@MOA.SCRC.Symbolics.COM> jrd@STONY-BROOK.SCRC.SYMBOLICS.COM (John R. Dunning) writes:
->I recently discovered why my ARC was behaving so strangely.  When I tell
->gulam "arc a foo *.c" gulam attempts to expand the "*.c" into "foo.c
->bar.c baz.c ...", and substitute that list of file names into the
->arglist before starting up ARC.  the problem, of course, is that if
->you've got very may files, gulam comes up with a ridiculously long
->arglist, and ends up trying to call ARC with a bogus argstring, or
->otherwise getting confused.

this is NOT a bug...this is the way gulam is s'posed to work (as does
sh and csh under unix). gulam expands any file wildcards (or more properly
regular expressions) before doing its system(3) call (or Pexec). if you
want arc to read the * in the command line, you must quote it thusly:

	arc a foo '*.c'

->Checking the GULAM doc reveals some stuff about how it's a feechur (as
->opposed to a bug in a tux) that it attempts to outsmart itself this way,
->but I couldn't find any way to disable the feechur.  Does anyone know if
->it's possible?

no, it didn't out smart itself, you just did not understand how the shell
works. just remember to quote and you should be alright. (ain't Unix 
wunnerful for new users? :^). the unix csh has a global variable called
'noglob' which inhibits this action. i don't think gulam has it so you
manually disable it with quotes.

-bill