X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :content-type:content-transfer-encoding; q=dns; s=default; b=Uqt vOO25rsgj/nR20swTXGAWl+y866wHjJIYsQiJ3N7SLC+PaYG9zwm0IdF07p4MCpa eNWCw+cQ/BSPNabjeq5YJXt6rVZrwxDkBDvCRChZzsTcNZn18Av5DTlloQSrUisW AWMGol+nseA5S3+qivhgO7L0keMymswWTe1NaRBE= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :content-type:content-transfer-encoding; s=default; bh=SJmmNwLNV QxkzOecIhBLfWeQ5l8=; b=tGKoON/Re/AQ2jmt5/o6hD8jO+0Qw9UGrHWDckJJA vHNIgbHHzyctZRGZxb+8qT4jSgaHILW6Q53UKp+YlnaTcsNUQLrS0lzZBnNAASG6 DS+0rThnr+B5ua8kdmatOIlj5M7LdiloaRHixtIMw/RPxAE0vV7wDUYfLBwM4ZKD Wg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: Ishtar.tlinx.org Message-ID: <5362C6A0.3040306@tlinx.org> Date: Thu, 01 May 2014 15:11:44 -0700 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: cygwin-bash compat/regression bug... startup line prob Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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. ---- That's why I commented that something was bogus. Here it is again: law.Bliss> cat /tmp/t.sh #!/bin/bash -u echo -e "Hello World\n" law.Bliss> 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: ---- 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 devolution. But NOTE -- the above error claims it is coming from /usr/bin/bash. That's not my login shell nor on the shebang line. That's cygwin-black-magic... converting all /bin paths to /usr/bin...even shells?... > > > Regarding how your script is executed: > > If you do "$ bash t.sh", the she-bang line is *ignored*, it's just a > comment in this case. --- I'm aware of that -- I was noting that the alternate ways of invoking it made a difference. Not that I didn't understand why. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple