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

Previous Next

Package: emacs;

Reported by: Michael Heerdegen <michael_heerdegen <at> web.de>

Date: Mon, 3 Jun 2019 02:28:02 UTC

Severity: normal

Tags: confirmed, fixed, patch

Found in version 27.0.50

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: npostavs <at> gmail.com
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 36068 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>
Subject: bug#36068: 27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected!
Date: Mon, 03 Jun 2019 09:50:47 -0400
tags 36068 + confirmed
quit

Michael Heerdegen <michael_heerdegen <at> web.de> writes:

> Noam Postavsky <npostavs <at> 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

Now any byte-compilation will report unescaped `?)'.  You can

    (setq lread--unescaped-character-literals nil)

to stop it.




This bug report was last modified 5 years and 348 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.