From: Michael Heerdegen <michael_heerdegen@web.de>
To: 39169@debbugs.gnu.org
Subject: bug#39169: 28.0.50; Confusing obsolete variable warnings in eieio-defclass-autoload
Date: Sat, 18 Jan 2020 10:57:24 +0100 [thread overview]
Message-ID: <87tv4txf23.fsf@web.de> (raw)
Hello,
I'm currently developing a Gnu Elpa package that makes use of
`defclass'. These lines in `eieio-defclass-autoload':
#+begin_src emacs-lisp
;; turn this into a usable self-pointing symbol
(when eieio-backward-compatibility
(set cname cname)
(make-obsolete-variable cname (format "use \\='%s instead" cname)
"25.1"))
#+end_src
(and eieio-backward-compatibility defaults to t) lead to the following
situation: when I have any class, for example, named `buffer-note', and
I have the generated autoloads loaded, whenever I use a variable with
the name `buffer-note' (which is a quite natural name for objects of
that class), I get tons of warnings saying:
| buffer-note.el:136:11:Warning: `buffer-note' is an obsolete
| variable (as of 25.1); use 'buffer-note
The purpose of these warnings is a backward compatibility one, but it
shoots way over target: these warnings prevent me from using the class
name as a variable name - I keep renaming variables to prevent these
annoying warnings all the time. They are obviously very confusing if
you don't know the background internals, unless you really have hit the
addressed case (and of course following the instruction is not
expedient). And it's hard to get rid of them: because the
`make-obsolete-variable' are in the autoloads, not even a file-local
eieio-backward-compatibility setting helps.
Please reconsider how these warnings are implemented. If no better
solution can be found, the warning message should at least be made more
meaningful and tell which case it addresses, and there should be a
(discoverable!) way to turn off these warnings (file locally).
TIA,
Michael.
In GNU Emacs 28.0.50 (build 23, x86_64-pc-linux-gnu, GTK+ Version 3.24.13, cairo version 1.16.0)
of 2020-01-17 built on drachen
Repository revision: 4d3ac4cddbe1960f5227d14bd0d357a7b19c1296
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12006000
System Description: Debian GNU/Linux bullseye/sid
next reply other threads:[~2020-01-18 9:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 9:57 Michael Heerdegen [this message]
2020-08-24 20:55 ` bug#39169: 28.0.50; Confusing obsolete variable warnings in eieio-defclass-autoload Lars Ingebrigtsen
2020-08-25 2:12 ` Stefan Monnier
2020-08-25 20:05 ` Lars Ingebrigtsen
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
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=87tv4txf23.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=39169@debbugs.gnu.org \
/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).