From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: unescaped character literals
Date: Thu, 08 Feb 2018 18:17:41 +0100 [thread overview]
Message-ID: <86mv0jl7t6.fsf@zoho.com> (raw)
In-Reply-To: mailman.8744.1518107626.27995.help-gnu-emacs@gnu.org
Andreas Röhler wrote:
> When opening Emacs26-pretest, get a message:
>
> unescaped character literals `?)' detected!
>
> AFAIU it refers to a test which contains
>
> (should (eq (char-before) ?))
Perhaps just escape it?
(should (eq (char-before) ?\)) ; t
?
--
underground experts united
http://user.it.uu.se/~embe8573
next parent reply other threads:[~2018-02-08 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8744.1518107626.27995.help-gnu-emacs@gnu.org>
2018-02-08 17:17 ` Emanuel Berg [this message]
2018-02-08 17:27 ` unescaped character literals Emanuel Berg
2018-02-08 17:33 ` Emanuel Berg
2018-02-08 17:50 ` Emanuel Berg
2018-02-08 17:55 ` Emanuel Berg
2018-02-08 19:11 ` John Mastro
[not found] ` <mailman.8748.1518117099.27995.help-gnu-emacs@gnu.org>
2018-02-08 19:41 ` Emanuel Berg
2018-02-08 16:32 Andreas Röhler
2018-02-08 20:44 ` Andreas Röhler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mv0jl7t6.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).