From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: "unescaped character literals detected" Date: Fri, 05 May 2017 19:49:06 +0000 Message-ID: References: <834lx0hekg.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a114115d8518b2d054ecc2f38 X-Trace: blaine.gmane.org 1494013814 18947 195.159.176.226 (5 May 2017 19:50:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 5 May 2017 19:50:14 +0000 (UTC) To: Eli Zaretskii , emacs-devel@gnu.org, Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 05 21:50:05 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d6jEq-0004h7-7R for ged-emacs-devel@m.gmane.org; Fri, 05 May 2017 21:50:04 +0200 Original-Received: from localhost ([::1]:48731 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d6jEw-0001ov-04 for ged-emacs-devel@m.gmane.org; Fri, 05 May 2017 15:50:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d6jEB-0001nu-KK for emacs-devel@gnu.org; Fri, 05 May 2017 15:49:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d6jEA-0008Pk-JE for emacs-devel@gnu.org; Fri, 05 May 2017 15:49:23 -0400 Original-Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:36375) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d6jE8-0008Ms-TP; Fri, 05 May 2017 15:49:21 -0400 Original-Received: by mail-lf0-x236.google.com with SMTP id h4so8896731lfj.3; Fri, 05 May 2017 12:49:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=lIkzDmqyBHwQ7sh3iMfDWEHW/ZBQS1soKp8IIhZWpxM=; b=nFbAEFaeMDXC0N3w214JLWgn/fW+1ET5rrwe6/L35SrMC9eAr1xUnhLzIBnXM4u3G/ Xe2JZm8fcc7fqhqt73br3nuODvUPePZmVP6w6FZyB9vSqn/t70ix1skbCq9z0PphspDa DfMZ3f69iCjGCaLrhXFLC2MYh7qF4mAaJHqXi9uEoFeGLHGgPCBSEK8paJUZVEutmrzb BYCqnQjB3pTAKInhp1RLCW0VLG6X+/wjRGNRB5yg8NuhbB9TRnAp2FZSxpqKx4w9I/Iz U/mmoeKjhMhzdHfWeNrWGRL1BSteM42VabMG+8Xt7uoKqT4qqhO2ytykjSbOMOIB1xaT yF+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=lIkzDmqyBHwQ7sh3iMfDWEHW/ZBQS1soKp8IIhZWpxM=; b=ZfCPAgNLrNPPJyuCyklix9lzfJ0nI9qYmFxV66cC6dGY2BZAztHlep+V3TiUbWpvgz Q9luPIGKsHFPp169iJbpA/7KTjuFVOqguwLeI3e43fgU1va2jtAUqcTYhv2x9ytgmKGr nm+qCSwKAJNR35g4tkcaL7q3S6WNdBKwYtzaKU09aDINST+fgHPFKyhawarrXNlvk74h 1jxgiTd/ba28temxuLraYnAG3YdrzuAng2Zpp5aF/GN6ITsViJCf+66agt27RXcNyK86 JFf+zHiOa2SPlEe9Lw4WXSNT5+L/+DRHfzXOZNsNFg4ZJMggDQeS+PFO0ay/TO1xhFqI 5jSQ== X-Gm-Message-State: AN3rC/40zOvejwrjX4jEXv1VnBhUlnSk0QHuyoQr9C3hBWR0PSewVxjJ k5tY27Zq5HhaLQ76qiuyva3QRGMzew== X-Received: by 10.25.160.147 with SMTP id j141mr15775136lfe.19.1494013757719; Fri, 05 May 2017 12:49:17 -0700 (PDT) In-Reply-To: <834lx0hekg.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4010:c07::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:214583 Archived-At: --001a114115d8518b2d054ecc2f38 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, May 4, 2017 at 10:39 AM Eli Zaretskii wrote: > Compiling the Lisp files in the current master produces quite a few of > these new warnings, see below. I hope someone is looking into > eliminating them, otherwise we introduced a safety feature that does > nothing except annoying us. > > Also, there seem to be several instances of the same warning, only one > of which points out the line number where the problem happens. Is it > possible to output only that final warning? The rest of them, those > without a line number, are useless, as there's no practical way of > finding the offending code unless you know exactly what to look for > (and the wording isn't specific enough to allow the latter). > +1 Now when I load verilog-mode.el (autoloaded when I open the SystemVerilog files), I get: Loading =E2=80=98verilog-mode=E2=80=99: unescaped character literals ; dete= cted! verilog-mode.el has 14.5k lines. It would be very helpful to print the line number where unescapted character literals are detected so that I can attempt to fix it. Thanks. PS: This was added in http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=3Dc2bbdc3316487e34eba= 1470dd059c0c290431e00, so copying Philipp. --=20 Kaushal Modi --001a114115d8518b2d054ecc2f38 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 4,= 2017 at 10:39 AM Eli Zaretskii <eliz@gn= u.org> wrote:
Compiling the = Lisp files in the current master produces quite a few of
these new warnings, see below.=C2=A0 I hope someone is looking into
eliminating them, otherwise we introduced a safety feature that does
nothing except annoying us.

Also, there seem to be several instances of the same warning, only one
of which points out the line number where the problem happens.=C2=A0 Is it<= br> possible to output only that final warning?=C2=A0 The rest of them, those without a line number, are useless, as there's no practical way of
finding the offending code unless you know exactly what to look for
(and the wording isn't specific enough to allow the latter).

+1

Now when I load veril= og-mode.el (autoloaded when I open the SystemVerilog files), I get:

Loading =E2=80=98verilog-mode=E2=80=99: unescaped charact= er literals ; detected!=C2=A0

verilog-mode.el has = 14.5k lines. It would be very helpful to print the line number where unesca= pted character literals are detected so that I can attempt to fix it.
=

Thanks.

--

Kaushal Modi

--001a114115d8518b2d054ecc2f38--