Re: strange linux problem
- Posted by Chris Burch <chriscrylex at aol.com> Feb 28, 2005
- 433 views
Alexander Toresson wrote: > > I'm in a directory which contains exu and some .exu files. I type: > > # ./exu ./foo.exu ./bar.exu > > then bash complains about the syntax of the euphoria script in ./bar.exu. > > If I type: > > # ./exu ./foo.exu 10 > > sh: line 1: 10: command not found > > > What is going on, and how can I make it understand that the second thing is > also an > argument? > Now it seems to think that it is a bash scripting command or path to a bash > script! > > Regards, Alexander Toresson > > Hi This looks to me like a combination of bash / exu / path probs Thoughts exu treats all command line arguments as parameters to your programs, so in other words you are passing bar.exu as an argument to foo. And also 10, which I don't fully understand. Try enclosing the arguments (in various combinations for what you want to achieve in quotes. eg ./exu "./foo.exu 10" or ./exu ./foo.exu "10" and see what happens If, in the first case, you are trying to execute two eu programs, one after the other, you need to type ./exu ./foo.exu : ./exu ./bar.exu Another thing, its slightly lower security, but you could set your path environment variable to include '.', that way bash will look in the current directory. However don't use this on a security conscious machine. eg in .Profile $PATH=$PATH;. export PATH This will allow you to use the current directory in your command, eg instead of ./exu ./foo.exu exu foo.exu Chris http://members.aol.com/chriscrylex/euphoria.htm http://uboard.proboards32.com/