From: Andrey Repin <anrdaemon@yandex.ru>
To: David Karr <davidmichaelkarr@gmail.com>, cygwin@cygwin.com
Subject: Re: Another confusing error from someone else's Cygwin setup
Date: Wed, 5 Jul 2023 22:25:23 +0300 [thread overview]
Message-ID: <1417059262.20230705222523@yandex.ru> (raw)
In-Reply-To: <CAA5t8VrR9yD3LS8AyRWD9O5J6gDbrfdbaWSUrjzwjYu30Umkiw@mail.gmail.com>
Greetings, David Karr!
> 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() {
> ---------------
Quick and dirty way to solve your issue -
$ tr -d '\r' > script.fixed < script.erring
> This was pretty perplexing,
It is actually pretty clear, though.
$ od -t x1a < script.erring
See the output.
--
With best regards,
Andrey Repin
Wednesday, July 5, 2023 22:22:57
Sorry for my terrible english...
prev parent reply other threads:[~2023-11-06 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:35 David Karr
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 [this message]
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=1417059262.20230705222523@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=davidmichaelkarr@gmail.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).