From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 39169@debbugs.gnu.org
Subject: bug#39169: 28.0.50; Confusing obsolete variable warnings in eieio-defclass-autoload
Date: Tue, 25 Aug 2020 22:05:26 +0200 [thread overview]
Message-ID: <87bliy4hkp.fsf@gnus.org> (raw)
In-Reply-To: <jwveenvmqfv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 24 Aug 2020 22:12:13 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> You mean we should change the default of `eieio-backward-compatibility`
> to nil?
No, I meant removing the warning, since we no longer have any in-tree
usage of this stuff (I think).
> Maybe you're right.
>
> We're currently removing things that were made obsolete in Emacs-23,
> whereas those were made obsolete in Emacs-25, but setting that var to
> nil is not as drastic as removing those vars and functions, so it's
> probably OK to do it already.
Hm... it does sound a bit drastic... But now I'm wondering why Michael
isn't just setting/binding eieio-backward-compatibility to nil? Then
the warnings would go away, and he probably aren't using the compat
symbols, anyway?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-25 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 9:57 bug#39169: 28.0.50; Confusing obsolete variable warnings in eieio-defclass-autoload Michael Heerdegen
2020-08-24 20:55 ` Lars Ingebrigtsen
2020-08-25 2:12 ` Stefan Monnier
2020-08-25 20:05 ` Lars Ingebrigtsen [this message]
2020-08-25 20:07 ` Lars Ingebrigtsen
2020-08-26 15:30 ` Michael Heerdegen
2020-08-27 13:34 ` Lars Ingebrigtsen
2020-08-27 15:07 ` Michael Heerdegen
2020-08-27 15:23 ` Michael Heerdegen
2020-08-27 21:22 ` Michael Heerdegen
2020-08-27 21:38 ` Stefan Monnier
2020-12-29 10:59 ` Michael Heerdegen
2021-01-06 16:56 ` Michael Heerdegen
2020-08-28 14:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bliy4hkp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39169@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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.