From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 43780@debbugs.gnu.org
Subject: bug#43780: 27.1; defvaralias and define-obsolete-variable-alias
Date: Tue, 6 Oct 2020 17:06:30 -0700 (PDT) [thread overview]
Message-ID: <b6b4cc0b-3609-4ac3-aa58-3c673ac5a2c8@default> (raw)
In-Reply-To: <877ds3hrpe.fsf@web.de>
> Since this bug report is just about one example; and since your tried
> "fix", when it had worked, would also have had an undesired global
> effect - what would be your favorite solution?
>
> Would it make sense if Emacs provided a file-local variable with which
> you could specify an Emacs version and the effect would be that for
> compiling that file all warnings about obsolete stuff would be
> suppressed if the obsolete declaration happened in an Emacs version
> newer than what you specified? So like
>
> ;;; byte-comp-suppress-obsolete 23.1
>
> would have the effect that only stuff that has been obsolete before 23.1
> would be reported?
Sorry, but I don't have a plan/solution.
IMHO, that variable should never have been renamed.
If the renaming (done in 27.1, for dubious reasons)
could be reverted that would be great. Or just
remove the obsolete part - have two aliases (no big
deal, and probably the best way to repair the damage
at this point).
The previous name was better, and in any case there
was no need (no good reason) to apply such a trivial,
gratuitous renaming, even if the new name were
(mistakenly) considered better.
See https://lists.gnu.org/archive/html/emacs-devel/2020-10/msg00326.html
I have no hope that this (trivial) bug (#43780) will
be fixed, and I have no other good solution for it
(besides removing the obsolete labeling).
Any code that uses the old name will lead to a compiler
warning now. So be it. I really wish this kind of
thing didn't happen. No good purpose was served.
That's really the lesson here. If that gets learned
somehow then the bother caused by this bug will have
been worth it.
next prev parent reply other threads:[~2020-10-07 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 18:16 bug#43780: 27.1; defvaralias and define-obsolete-variable-alias Drew Adams
2020-10-05 7:47 ` Lars Ingebrigtsen
2020-10-05 16:27 ` Drew Adams
2020-10-06 21:41 ` Michael Heerdegen
2020-10-06 22:54 ` Drew Adams
2020-10-06 23:15 ` Michael Heerdegen
2020-10-07 0:06 ` Drew Adams [this message]
2020-10-07 23:13 ` Michael Heerdegen
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=b6b4cc0b-3609-4ac3-aa58-3c673ac5a2c8@default \
--to=drew.adams@oracle.com \
--cc=43780@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).