From: Michael Heerdegen <michael_heerdegen@web.de>
To: "T.V Raman" <raman@google.com>
Cc: rtt@dasyatidae.com, emacs-devel@gnu.org
Subject: Re: possibly spurious bytecomp warning:
Date: Sat, 20 May 2023 04:03:06 +0200 [thread overview]
Message-ID: <87a5xzdajp.fsf@web.de> (raw)
In-Reply-To: <25704.9876.842054.498789@retriever.mtv.corp.google.com> (T. V. Raman's message of "Fri, 19 May 2023 18:47:00 -0700")
"T.V Raman" <raman@google.com> writes:
> Thanks for the explanation -- makes sense. Perhaps we should have a
> keymap related API call that allows one to remove keymap entries?
Doesn't `define-key' suffice?
Let me add that these warnings were discussed in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61730
If anyone has a considered opinion why such warnings are a good/ a bad
idea: It is not yet cast in concrete.
Michael.
next prev parent reply other threads:[~2023-05-20 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 20:48 possibly spurious bytecomp warning: T.V Raman
2023-05-19 22:19 ` Michael Heerdegen
2023-05-19 23:36 ` Robin Tarsiger
2023-05-20 0:26 ` Michael Heerdegen
2023-05-20 1:47 ` T.V Raman
2023-05-20 2:03 ` Michael Heerdegen [this message]
2023-05-20 19:31 ` T.V Raman
2023-05-21 0:44 ` Michael Heerdegen
2023-05-21 2:03 ` T.V Raman
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=87a5xzdajp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=rtt@dasyatidae.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).