Eric Blake wrote:
On 05/01/2014 04:11 PM, Linda Walsh wrote:
The reason the above fails... (I got it to work).. is that if there is a
space
on the line after the "-u", that also fails.
I didn't deliberately put one there, but that it no longer handles
separate options is an evolution of softwa
Eric Blake wrote:
So why doesn't a single argument work (-u?)
Because you didn't pass a single argument, but left trailing space ...
---
But looking at the file, I didn't notice that until
I recreated the file w/o using cut/paste (i.e. happened
in another script that had -u at the top, and I
On 05/01/2014 04:11 PM, Linda Walsh wrote:
> The reason the above fails... (I got it to work).. is that if there is a
> space
> on the line after the "-u", that also fails.
>
> I didn't deliberately put one there, but that it no longer handles
> separate options is an evolution of software devolu
Bob McGowan wrote:
>> Because you weren't running /bin/bash at that point in time, but
>> /usr/bin/bash. Again, you snipped the relevant portion of your original
>
> No...I was... the output at the top was from "t.sh", which had
> #!/bin/bash.
>
> But the error message says /usr/bin/bash.
On 05/01/2014 12:11 PM, Linda Walsh wrote:
>
> On linux, (and, thus on cygwin?), "#!/bin/bash -u -x -a -b -c"
> is passed as 1 argument to bash. I.e. the spaces don't break things
> into separate arguments on linux.
Correct. So follow it through to it's logical conclusion:
/bin/bash "-u -x -a
Eric Blake wrote:
On 04/30/2014 11:57 PM, Linda Walsh wrote:
Eric Blake wrote:
On 04/28/2014 02:43 PM, Linda Walsh wrote:
cat bin/t.sh
#!/bin/bash -u
Um... it doesn't work with 1 argument either.
Your context quoting is hard to follow. Here, you are complaining about
a she-bang with only
On 04/30/2014 11:57 PM, Linda Walsh wrote:
> Eric Blake wrote:
>> On 04/28/2014 02:43 PM, Linda Walsh wrote:
>>
>> >> cat bin/t.sh
>> > #!/bin/bash -u
> Um... it doesn't work with 1 argument either.
Your context quoting is hard to follow. Here, you are complaining about
a she-bang with only one a
Eric Blake wrote:
On 04/28/2014 02:43 PM, Linda Walsh wrote:
>> cat bin/t.sh
> #!/bin/bash -u
Um... it doesn't work with 1 argument either.
This is an invalid shebang line. Historically, you are allowed at most
ONE argument to the program that you will be executing.
?!?
Historically?.. sin
On 04/28/2014 02:43 PM, Linda Walsh wrote:
>> cat bin/t.sh
> #!/bin/bash -u -x
This is an invalid shebang line. Historically, you are allowed at most
ONE argument to the program that you will be executing.
#!/bin/bash -ux
is valid,
#!/bin/bash -u -x
is not.
> If I run it via:
>> bash t.sh
This 'used' to work...but doesn't now: -- running
bash with the "-u" flag:
t.sh
/usr/bin/bash: - : invalid option
Usage: /usr/bin/bash [GNU long option] [option] ...
/usr/bin/bash [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--
10 matches
Mail list logo
