public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cygwin-bash compat/regression bug...  startup line prob
Date: Mon, 28 Apr 2014 21:18:00 -0000	[thread overview]
Message-ID: <535EC59E.9080602@redhat.com> (raw)
In-Reply-To: <535EBD61.5080109@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

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
> Hello World

When you run it in this manner, you are NOT using the shebang line, but
are instead using the 'bash' found on a PATH search, which explains:

>>
> ---works---
> Also weird -- the interp line says "/bin/bash" not "/usr/bin/bash"
> as the shell, so why does the error come from /usr/bin/bash?

the answer to this question.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2014-04-28 21:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 20:43 Linda Walsh
2014-04-28 21:18 ` Eric Blake [this message]
2014-05-01  5:57   ` Linda Walsh
2014-05-01  6:41     ` Eric Blake
2014-05-01 18:11       ` Linda Walsh
2014-05-01 20:41         ` two execve() inconsistencies [was: cygwin-bash compat/regression bug... startup line prob] Eric Blake
2014-05-02 21:44           ` two execve() inconsistencies (was cygwin-bash compat/regression bug... startup line prob) Linda Walsh
2014-05-01 22:11 cygwin-bash compat/regression bug... startup line prob Linda Walsh
2014-05-02  1:33 ` Eric Blake
2014-05-03 19:01   ` Linda Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=535EC59E.9080602@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).