From: Stefan Monnier <monnier@iro.umontreal.ca>
To: larsi@gnus.org
Cc: Stefan Kangas <stefan@marxist.se>,
Emacs developers <emacs-devel@gnu.org>
Subject: with-suppressed-warnings ineffective?
Date: Tue, 19 Nov 2019 09:50:04 -0500 [thread overview]
Message-ID: <jwvwobw6iby.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmnqgiyxjJ6hHx7F6ogTBR7Lw+O9u4=uTkQHX-BiR9OLfg@mail.gmail.com> (Stefan Kangas's message of "Mon, 18 Nov 2019 16:07:45 +0100")
Hi Lars,
Another brilliant Stefan pointed out that we have undesired warnings:
ELC cedet/semantic/bovine/c.elc
‘define-child-mode’ is an obsolete macro (as of 27.1); use ‘define-derived-mode’ instead.
ELC cedet/semantic/bovine/el.elc
‘define-child-mode’ is an obsolete macro (as of 27.1); use ‘define-derived-mode’ instead.
[ Not sure if the file names are right above. ]
AFAICT these come from
(with-suppressed-warnings ((obsolete define-child-mode))
;; FIXME: We should handle this some other way!
(define-child-mode c++-mode c-mode
"`c++-mode' uses the same parser as `c-mode'."))
and
(with-suppressed-warnings ((obsolete define-child-mode))
;; FIXME: We should handle this some other way!
(define-child-mode lisp-mode emacs-lisp-mode
"Make `lisp-mode' inherit mode local behavior from `emacs-lisp-mode'."))
Any idea why the `with-suppressed-warnings` doesn't actually suppress
the warning? Any hope you could fix it?
Stefan
next prev parent reply other threads:[~2019-11-19 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191025030629.28499.81989@vcs0.savannah.gnu.org>
[not found] ` <20191025030630.EF0EA20C1E@vcs0.savannah.gnu.org>
2019-11-18 15:07 ` master f131e39: * lisp/cedet/mode-local.el: Clean up name space Stefan Kangas
2019-11-19 14:50 ` Stefan Monnier [this message]
2019-11-20 11:29 ` with-suppressed-warnings ineffective? Lars Ingebrigtsen
2019-11-20 13:45 ` Stefan Monnier
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=jwvwobw6iby.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--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 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).