From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: phst@google.com, wsnyder@wsnyder.org, emacs-devel@gnu.org,
kaushal.modi@gmail.com
Subject: Re: Help fix unescaped character literals detected warnings in verilog-mode (Was: Re: "unescaped character literals detected")
Date: Sun, 07 May 2017 19:36:41 +0300 [thread overview]
Message-ID: <83inlcei92.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkR277jXosWhKXqJb2Pth0-ikT0KbRWxV7utz19UuDWXmA@mail.gmail.com> (message from Philipp Stephani on Sun, 07 May 2017 12:36:54 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sun, 07 May 2017 12:36:54 +0000
>
> Philipp Stephani <phst@google.com> schrieb am Fr., 5. Mai 2017 um 23:35 Uhr:
>
> Kaushal Modi <kaushal.modi@gmail.com> schrieb am Fr., 5. Mai 2017 um 22:14 Uhr:
>
> On Fri, May 5, 2017 at 4:02 PM Philipp Stephani <phst@google.com> wrote:
>
> You should change it to ?\;
> I.e. escape the ; not the ?
>
> Thanks for the explanation. As I understand, you will be fixing all of these?
>
> Yes, the ones that are in the Emacs repo.
>
> These should now be fixed with 3c4c8ca06e3306ccbcd07e354eb51abe53b52d22.
Thanks.
next prev parent reply other threads:[~2017-05-07 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 14:38 "unescaped character literals detected" Eli Zaretskii
2017-05-05 19:49 ` Kaushal Modi
2017-05-05 20:00 ` Help fix unescaped character literals detected warnings in verilog-mode (Was: Re: "unescaped character literals detected") Kaushal Modi
2017-05-05 20:02 ` Philipp Stephani
2017-05-05 20:14 ` Kaushal Modi
2017-05-05 21:35 ` Philipp Stephani
2017-05-07 12:36 ` Philipp Stephani
2017-05-07 12:48 ` Kaushal Modi
2017-05-07 16:36 ` Eli Zaretskii [this message]
2017-05-05 20:33 ` Help fix unescaped character literals detected warnings in verilog-mode Stefan Monnier
2017-05-06 22:44 ` Richard Stallman
2017-05-13 10:31 ` Philipp Stephani
2017-05-05 20:04 ` "unescaped character literals detected" Philipp Stephani
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=83inlcei92.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=p.stephani2@gmail.com \
--cc=phst@google.com \
--cc=wsnyder@wsnyder.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).