Re: bash shell script: recently running, now failing

Greetings, Brian Inglis via Cygwin! > On 2023-04-06 06:21, Andrey Repin via Cygwin wrote: >>> I have a "hash bang" bash shell script i.e. first line >>> #! /bin/sh >>> or equivalently >>> #! /bin/bash >> By default, sh is bash in base Cygwin installation. >>> Q3 - at 1/8 the size of bash and

Re: bash shell script: recently running, now failing

On 2023-04-06 06:21, Andrey Repin via Cygwin wrote: I have a "hash bang" bash shell script i.e. first line #! /bin/sh or equivalently #! /bin/bash By default, sh is bash in base Cygwin installation. Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and reach of dash.

Re: bash shell script: recently running, now failing

Coming from an enterprise and supercomputing background, we were able to control what shell was available, so bashisms weren't a problem any more than dashisms, fishisms, kornisms, perl or python versionisms, etc, might be. But, when I was in a commercial environment, everything - shell, perl, C,

Re: bash shell script: recently running, now failing

On Thu, Apr 06, 2023 at 04:43:51AM +, Fergus Daly via Cygwin wrote: > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash > For various reasons I want this file to be identified as binary so its second > line > is the single character null \x00

Re: bash shell script: recently running, now failing

Greetings, Fergus Daly! > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash By default, sh is bash in base Cygwin installation. > Q3 - at 1/8 the size of bash and sh, I am not at all sure of the role and > reach of dash. > Should the edit

Re: bash shell script: recently running, now failing

Place the nul on the third line. For example: #!/bin/bash # # ^@ identify as a binary file ... On Thu, Apr 6, 2023 at 4:03 AM Corinna Vinschen via Cygwin < cygwin@cygwin.com> wrote: > On Apr 6 04:43, Fergus Daly via Cygwin wrote: > > I have a "hash bang" bash shell script i.e. first line > >

Re: bash shell script: recently running, now failing

On Apr 6 04:43, Fergus Daly via Cygwin wrote: > I have a "hash bang" bash shell script i.e. first line > #! /bin/sh > or equivalently > #! /bin/bash > For various reasons I want this file to be identified as binary so its second > line > is the single character null \x00 showing up in some

bash shell script: recently running, now failing

I have a "hash bang" bash shell script i.e. first line #! /bin/sh or equivalently #! /bin/bash For various reasons I want this file to be identified as binary so its second line is the single character null \x00 showing up in some editors e.g. nano as ^@ This does not prevent the script from