Spurious warning generated by bash
Soren
somian08@gmail.com
Thu Jan 1 02:20:41 GMT 2026
Wow, yes.
Backwoods BC wrote:
> I suspect your source is UTF with a BOM tag.
You are absolutely correct. I opened the script in vim and :set nobomb and
the script now executes properly without the annoying noise. I needed the
bomb for something to do with perl developing (it was a while ago), but
I'll have to remember to set vim up so that it doesn't do that on scripts.
Thank you VERY much and have a Happy New Year.
- Soren
On Wed, Dec 31, 2025 at 7:59 PM Backwoods BC via Cygwin <cygwin@cygwin.com>
wrote:
> On Wed, Dec 31, 2025 at 1:25 PM David Dyck via Cygwin <cygwin@cygwin.com>
> wrote:
> >
> > On Wed, Dec 31, 2025 at 12:21 PM Soren via Cygwin <cygwin@cygwin.com>
> wrote:
> >
> > >
> > > ./list2str.sh: line 1: #!/bin/bash: No such file or directory
> > >
> >
> > nice perl script :-)
> > I don't get the warning when the script is run from bash
> > what context did you run the script from?
>
> I suspect your source is UTF with a BOM tag. I created a file with
> this and got your exact results. UTF is OK as long as it doesn't have
> the BOM tag.
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
More information about the Cygwin
mailing list