all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@gmail.com
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 36068@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#36068: 27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected!
Date: Mon, 03 Jun 2019 09:50:47 -0400	[thread overview]
Message-ID: <8536kqdbgo.fsf@gmail.com> (raw)
In-Reply-To: <8736kqu7uy.fsf@web.de> (Michael Heerdegen's message of "Mon, 03 Jun 2019 15:16:37 +0200")

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

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

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

to stop it.





  reply	other threads:[~2019-06-03 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  2:14 bug#36068: 27.0.50; Warning: unescaped character literals `?)' detected, `?\)' expected! Michael Heerdegen
2019-06-03 12:06 ` Noam Postavsky
2019-06-03 13:16   ` Michael Heerdegen
2019-06-03 13:50     ` npostavs [this message]
2019-06-03 14:34       ` Michael Heerdegen
2019-06-03 14:51       ` Eli Zaretskii
2019-06-03 17:04         ` Andreas Schwab
2019-06-03 17:14           ` npostavs
2019-06-03 17:18       ` Andreas Schwab
2019-06-05  1:29         ` Noam Postavsky
2019-06-10 22:41           ` Noam Postavsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8536kqdbgo.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=36068@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.