ferdnyc left a comment (rpm-software-management/rpm#3661)
I wonder if this is user error? Does `%{escape:}` _eat_ backslashes? Do they
need to be doubled in its arguments, to get them to be included correctly when
the macro is expanded? Perhaps there really are backslashes missing from the
code
ferdnyc created an issue (rpm-software-management/rpm#3661)
**Describe the bug**
When viewing the Lua scripting attached to glibc-common on Fedora, the
displayed Lua code is lacking all of its backslash escapes, with every `\n`
being displayed as simply `n`.
**To Reproduce**
Steps to reproduce
ferdnyc left a comment (rpm-software-management/rpm#3661)
So, this is confusing. `rpm -q --scripts glibc` displays ***some*** code with
backslashes intact, and other code without:
```bash
$ rpm -q --scripts glibc
postinstall scriptlet (using ):
-- 8<---snip---8<
function update_gconv_modules_cac
