From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Noam Postavsky <npostavs@users.sourceforge.net>,
John Williams <jrw@pobox.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
26486@debbugs.gnu.org
Subject: bug#26486: 25.1.91; unused var warning from cconv.el can't be suppressed
Date: Tue, 06 Jul 2021 20:53:52 +0100 [thread overview]
Message-ID: <875yxn43sf.fsf@tcd.ie> (raw)
In-Reply-To: <87mtr0x025.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Mon, 05 Jul 2021 17:17:06 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Noam Postavsky <npostavs@users.sourceforge.net> writes:
>
>> This happens also without a macro.
>>
>> ;; -*- lexical-binding: t; byte-compile-warnings: nil -*-
>> (with-no-warnings (let (unused)))
>
> This currently gives a warning about both an unused variable and an
> empty let body.
>
> The following seemingly straightforward patch fixes both these things,
> I'd appreciate it if somebody had a look over it first, though. :-)
> (So Stefan M added to the CCs.)
I suspect this patch causes the following:
$ cat foo.el
;;; foo.el --- foo -*- lexical-binding: t -*-
(let ())
;;; foo.el ends here
$ emacs -Q -script foo.el
Eager macro-expansion failure: (void-function byte-compile-warning-enabled-p)
Thanks,
--
Basil
next prev parent reply other threads:[~2021-07-06 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 18:59 bug#26486: 25.1.91; spurious warnings from cconv.el John Williams
2017-04-13 19:28 ` Noam Postavsky
2021-07-05 15:17 ` bug#26486: 25.1.91; unused var warning from cconv.el can't be suppressed Lars Ingebrigtsen
2021-07-05 15:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-06 14:48 ` Lars Ingebrigtsen
2021-07-06 19:53 ` Basil L. Contovounesios [this message]
2021-07-06 20:03 ` Lars Ingebrigtsen
2021-07-06 20:04 ` Lars Ingebrigtsen
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=875yxn43sf.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=26486@debbugs.gnu.org \
--cc=jrw@pobox.com \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@users.sourceforge.net \
/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).