Subj : Re: about to blow a gaske To : Sniper From : Grymmjack Date : Sat May 21 2005 01:56 pm > > bash: *: ambiguous redirect > > So, its safe. :) > AM> Yea -- I built a machine and tried it. I got the same result. The '> > AM> *' looks like it should truncate all files. '> filename.ext' truncates > AM> the named file, due to a quirk of redirection. I think if '*' were to > AM> evaluate to a single filename, that would occur. If you do this: > > first.ext second.ext third.ext fourth.ext etcetera.ext > AM> then the shell should try to truncate 'first.ext', then execute > AM> 'second.ext' with 'third.ext fourth.ext etcetera.ext' as arguments and > AM> redirect STDOUT to 'first.ext'. > AM> I'm not sure why '*' evaluated to a list of files, doesn't bring about > AM> the same result. from what i recall, "*" does work like you expect it to. atleast when i ran mpl "*" it would compile all my .mps scripts in my /mystic/scripts directory but mpl * did not work. hrm. > I had totally forgotten what "> filename" would do... :) Wow! :) I'm > getting rusty. Glad it didn't wipe out my system... Damn... I just put > up a stupid sign... Ok! :) i apologize if i caused any problems.. i was simply being geeky. i commonly do basic stuff like that in a geeky context. it was as i stated earlier intended to be interpreted like this: less is greater than all things. sorry :( - grymmjack .