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: Tue, 06 Oct 2020 23:41:17 +0200 [thread overview]
Message-ID: <877ds3rq0y.fsf@web.de> (raw)
In-Reply-To: <d3a13330-e8ba-40d3-8b69-b11fe8a194c3@default> (Drew Adams's message of "Sat, 3 Oct 2020 11:16:25 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Please tell me the best way to leave my code alone, using
> `inhibit-null-byte-detection', and yet eliminate (only) this
> byte-compiler warning.
>
> Should I just use (put 'inhibit-null-byte-detection
> 'byte-obsolete-variable nil)?
>
> Ideally I'd want to affect only byte-compilation of the given file, and
> not want to globally change whether `inhibit-null-byte-detection' is
> considered obsolete.
>
> This is a serious question, not rhetorical.
I guess one could try to use `byte-compile--suppressed-warnings' as a
file-local variable, but it has an "internal" name. AFAIK you can turn
off compiler warnings regarding obsolete names completely per file, or
locally with `with-suppressed-warnings'. Is that acceptable?
Michael.
next prev parent reply other threads:[~2020-10-06 21:41 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 [this message]
2020-10-06 22:54 ` Drew Adams
2020-10-06 23:15 ` Michael Heerdegen
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=877ds3rq0y.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).