From: David Karr <davidmichaelkarr@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Another confusing error from someone else's Cygwin setup
Date: Mon, 26 Jun 2023 16:35:33 -0700 [thread overview]
Message-ID: <CAA5t8VrR9yD3LS8AyRWD9O5J6gDbrfdbaWSUrjzwjYu30Umkiw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
I'm seeing a problem with someone else's Cygwin setup, sort of similar to a
problem I asked about a couple of weeks ago, in that it's a problem with
the same user, but seemingly a completely different problem.
He is using a Bash script that I wrote, and he gets a seemingly nonsensical
error that I don't understand.
The script starts out pretty simply, just like this:
------------------
#! /bin/bash
#set -x
main() {
if [ "$1" == "" ]; then
usage;
exit;
fi
...
-----------------
He was getting a weird error on line 3, just saying this:
---------------------
...: line 3: syntax error near unexpected token `$'{\r''
...: line 3: `main() {
---------------
This was pretty perplexing, so I asked him to uncomment the "set -x" line
to see if that provided any useful information, and that fails with a
different error:
-------------------
: invalid option...: line 2: set: -
set: usage: set [-abefhkmnptuvxBCEHPT] [-o option-name] [--] [-] [arg ...]
------------------
This also makes no sense to me. I compared our "uname -a" outputs, and
they are almost identical. However, I then had him run "bash --version",
and I compared it to mine. Ironically, I'm using an OLDER version of bash
than he is. I'm on v4.4.12(3)-release, and he's on v5.2.15(3)-release. Is
there something in 5.x versions of Bash that could cause these issues?
next reply other threads:[~2023-06-26 23:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:35 David Karr [this message]
2023-06-26 23:58 ` Dan Harkless
2023-06-27 0:01 ` Dan Harkless
2023-06-27 2:08 ` Mike Gran
2023-06-27 17:52 ` David Karr
2023-07-05 19:25 ` Andrey Repin
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=CAA5t8VrR9yD3LS8AyRWD9O5J6gDbrfdbaWSUrjzwjYu30Umkiw@mail.gmail.com \
--to=davidmichaelkarr@gmail.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).