Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Bug/Feature in globbing
Message-ID: <8907142234.AA00396@aurel.caltech.edu>
Date: 14 Jul 89 22:34:12 GMT
References: <TALE.89Jul14112022@imagine.pawl.rpi.edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu
   Date: 14 Jul 89 15:20:22 GMT
   From: tale@rpi.edu  (David C Lawrence)
   References: <5476@videovax.tv.tek.com>,
        <8907141311.AA07040@aurel.caltech.edu>
   Sender: bug-bash-request@prep.ai.mit.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 19


   From: tektronix!tekcrl!tekfdi!videovax!bart@cis.ohio-state.edu  (Bart Massey)
   Bart> 	   for i in *
   Bart> 	   do
   Bart> 		   cat $i
   Bart> 	   done

   In <8907141311.AA07040@aurel.caltech.edu> bfox@AUREL.CALTECH.EDU (Brian Fox):
   BF> I'm really amazed that you would want this behaviour. In the above `for'
   BF> command, with "nullglobok" non-null, and no files in the current
   BF> directory, the `cat' would hang, waiting for input, since `$i' would
   BF> expand to nothing.

   Ugh.  I've never come up against a for loops that started with a null
   item in sh programming, but is that really what it is supposed to do?

No, and I take it back.  It doesn't do that.  Sorry.

Brian Fox