Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Janek Mi <janekmi@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Filename expansion bug
Date: Thu, 8 Aug 2019 16:33:16 +0200
Lines: 23
Approved: bug-bash@gnu.org
Message-ID: <mailman.1065.1565274812.1985.bug-bash@gnu.org>
References: <CABN8V7MFbLErHGDJTq0fsBJwS8nofcT8+jcd1LQf1QBq_GTPHQ@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Cc: marcin.slusarz@gmail.com
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Precedence: list
Xref: csiph.com gnu.bash.bug:15311

For some time in my scripts I was using something like this:

```shell
#!/usr/bin/env bash
shopt -s failglob
command="echo xyz\(\)"
$command
```

And it was working fine. But somewhere between bash version 4 and 5 I
realized it generates an error:
no match: xyz\(\)

with exit code equal 1.

If I understand correctly \( character should not trigger filename
expansion.
Any ideas?

Appendix:
```eval '$command'``` is causing the same issue whereas ```eval
"$command"``` works the same as bash 4 without filename expansion. Changing
the quotation mark character makes a huge difference.