From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: byte-compile-warn-obsolete
Date: Mon, 22 Aug 2022 12:22:09 +0200 [thread overview]
Message-ID: <87bkscbmsu.fsf@gnus.org> (raw)
In-Reply-To: <87v8qlf4ic.fsf@yahoo.com> (Po Lu's message of "Mon, 22 Aug 2022 09:31:23 +0800")
Po Lu <luangruo@yahoo.com> writes:
> I got the following warning this morning:
>
> In byte-compile-warn-obsolete:
> emacs-lisp/bytecomp.el:1358:8: Warning: function
> byte-compile-warn-obsolete used to take 1 argument, now takes 2
It'll be gone in the next compilation.
> Maybe TYPE should be made optional?
I thought it was unlikely to be used outside the Emacs tree, so I didn't
make it optional.
prev parent reply other threads:[~2022-08-22 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8qlf4ic.fsf.ref@yahoo.com>
2022-08-22 1:31 ` byte-compile-warn-obsolete Po Lu
2022-08-22 10:22 ` Lars Ingebrigtsen [this message]
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=87bkscbmsu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
/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).