bash undocumented syntax error

Linux for blind general discussion blinux-list at
Sun Jan 13 18:44:14 UTC 2019

Yeah, an error of this type is hard enough to debug when you have
access to the buggy code. Debugging from the error message alone is
nearly impossible in cases like this.

I will mention, however, that bash, and many other shells/scripting
languages, aren't picky about single quotes versus double quotes in
general, but can be quite picky that they're used consistently. E.g.
if you start a string literal with single quotes, you'd better end it
with single quotes, and if you start it with double quotes, you'd
better end it with double quotes, but bash probably doesn't care which
you use as long as the beginning and ending delimiters are the same.

Probably about the best advice I can give without examining the code directly.


On 1/13/19, Linux for blind general discussion <blinux-list at> wrote:
> On Sun, 13 Jan 2019, Linux for blind general discussion wrote:
>> The man page has nothing on unexpected end of file in it; searching for
>> unexpected in that man page provides no mention of unexpected.
> Possibly I've missed the context for this if it's a new thread resulting
> from a previous one (I am not up-to-date on this list).
> The error seems pretty self-explanatory.  Bash expected more input when it
> reached the end.
> I would expect that it was either looking for a closing quote (single or
> double) or a closing bracket of some sort.
> what are you trying to do?
> Cheers,
> Geoff.
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at

More information about the Blinux-list mailing list