bug#36068: 27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected!

[Andreas Schwab]

On Jun 03 2019, npostavs@gmail.com wrote:

> tags 36068 + confirmed
> quit
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> Noam Postavsky <npostavs@gmail.com> writes:
>>
>>> Hmm, is lread--unescaped-character-literals non-nil?  It looks like
>>> the variable can only get cleared due to the let-binding in load, so
>>> if it somehow got set outside of that, then you would see continual
>>> warnings from it.
>>
>> Yes, its value is (41).
>
> Ah, I think the problem can be triggered any time you `read' an unescaped
> literal outside of `load'.  E.g., from emacs -Q:
>
>     M-: (read "?)") RET
>
> or even just
>
>     M-: ?) RET

Even byte-compiling a file containing such an unescaped literal sets
lread--unescaped-character-literals in the global scope.  I think this
is where the real bug is.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."