From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 43780@debbugs.gnu.org
Subject: bug#43780: 27.1; defvaralias and define-obsolete-variable-alias
Date: Wed, 07 Oct 2020 01:15:09 +0200 [thread overview]
Message-ID: <877ds3hrpe.fsf@web.de> (raw)
In-Reply-To: <015ba27a-25b0-402d-b23e-ef358b586540@default> (Drew Adams's message of "Tue, 6 Oct 2020 15:54:07 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> No. I don't want to turn off all warnings just to be
> able to take care of this one.
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?
Michael.
next prev parent reply other threads:[~2020-10-06 23:15 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 [this message]
2020-10-07 0:06 ` Drew Adams
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=877ds3hrpe.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=43780@debbugs.gnu.org \
--cc=drew.adams@oracle.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).