Path: utzoo!utgpu!watmath!att!dptg!rutgers!iuvax!mailrus!cornell!uw-beaver!fluke!foot From: foot@tc.fluke.COM (Andrew Proudfoot) Newsgroups: comp.bugs.sys5 Subject: Re: ksh bugs Keywords: ksh Message-ID: <10234@fluke.COM> Date: 9 Aug 89 19:20:41 GMT References: <10166@fluke.COM> Distribution: na Organization: John Fluke Mfg. Co., Inc., Everett, WA Lines: 31 In article <10166@fluke.COM>, I wrote: > > >2. the "read" command does filename expansion on its input! > Just filename expansion; it doesn't do quote removal or tilde expansion. > This happens only on the Suns, not on the Vaxes. > > $ ls /usr0/foot/xx > file1 file2 file3 > $ while read stuff; do echo $stuff; done << EOF > > /usr0/foot/xx/* > > EOF > /usr0/foot/xx/file1 /usr0/foot/xx/file2 /usr0/foot/xx/file3 > No, wait, turn off the flamethrowers!! I was confused. This is normal behavior, not a bug, and it really does work the same on both our Suns and our Vaxes. The filename expansion isn't happening when the "read" command is interpreted, but when the "echo" command is: echo $stuff => echo /usr0/foot/xx/* (parameter substitution) => echo /usr0/foot/xx/file1... (filename generation) Items 1 and 3 still look like bugs to me, however. I'll talk to the toolchest people, as suggested by one of the repliers. Andy Proudfoot || domain: foot@tc.fluke.COM John Fluke Mfg. Co., M/S 223B || uucp: {uw-beaver,microsof,sun}!fluke!foot PO Box C9090 || Everett, WA 98206 || phone: (206) 356-5446