On Wed, May 30, 2018 at 2:25 AM, John Calcote <john.calcote@xxxxxxxxx> wrote:
> I've tried escaping with backslash, I've tried quoting with single quotes,
> I've tried escaping within double quotes. Nothing works. It seems the
> unquoting functionality will not be tricked into allowing a special
> character to be escaped.
>
> Any ideas?
I don't know if it works in your situation but another way of
"escaping" a special character is to assign it to a shell variable,
e.g. do
bang='!'
somewhere and later refer to ${bang}. This may work if variable
expansion takes place at a later stage than when the special
characters in question are processed.
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
