From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 36568@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#36568: with-suppress-warnings not working in seq-tests.el
Date: Wed, 07 Oct 2020 07:18:42 +0200 [thread overview]
Message-ID: <87362q8vgt.fsf@gnus.org> (raw)
In-Reply-To: <87mu0y4ork.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 07 Oct 2020 06:57:03 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Debugger entered--Lisp error: (void-function internal--with-suppressed-warnings)
> signal(void-function (internal--with-suppressed-warnings))
> apply(signal (void-function (internal--with-suppressed-warnings)))
Ah, this is due to
(defvar byte-compile-initial-macro-environment
...
(with-suppressed-warnings
. ,(lambda (warnings &rest body)
;; We let-bind `byte-compile--suppressed-warnings' here in order
;; to affect warnings emitted during macroexpansion.
;; Later `internal--with-suppressed-warnings' binds it again, this
;; time in order to affect warnings emitted during the
;; compilation itself.
(let ((byte-compile--suppressed-warnings
(append warnings byte-compile--suppressed-warnings)))
;; This function doesn't exist, but is just a placeholder
;; symbol to hook up with the
;; `byte-hunk-handler'/`byte-defop-compiler-1' machinery.
`(internal--with-suppressed-warnings
',warnings
,(macroexpand-all `(progn ,@body)
macroexpand-all-environment))))))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-07 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 3:23 bug#36568: with-suppress-warnings not working in seq-tests.el Stefan Kangas
2019-07-10 3:42 ` Stefan Kangas
2020-08-22 14:14 ` Lars Ingebrigtsen
2020-10-07 4:57 ` Lars Ingebrigtsen
2020-10-07 5:18 ` Lars Ingebrigtsen [this message]
2020-10-07 5:35 ` Michael Heerdegen
2021-12-05 3:22 ` Lars Ingebrigtsen
2021-12-05 11:27 ` Stefan Kangas
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=87362q8vgt.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36568@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.