From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juri Linkov <juri@linkov.net>
Cc: vaidheeswaran.chinnaraju@gmail.com, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Kaushal <kaushal.modi@gmail.com>
Subject: Re: Suggestion to have highlight related bindings consistent between search-map and hi-lock-map
Date: Thu, 30 Jul 2015 18:48:11 -0400 [thread overview]
Message-ID: <jwvsi85clir.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r3nqk34p.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 30 Jul 2015 01:31:02 +0300")
> Do we have a 2-step deprecation process where the first step
> is to warn the users about the planned changes by issuing
> a message like “use the new key instead” like we do with
> ‘define-obsolete-function-alias’ and ‘make-obsolete-variable’?
No, for key-bindings we just make the change, since we don't pay nearly
as much attention to breaking "user compatibility" (which can be fixed
with a define-key in ~/.emacs).
OTOH if the change ends up breaking third-party packages it might be
more problematic.
Stefan
next prev parent reply other threads:[~2015-07-30 22:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 19:02 Suggestion to have highlight related bindings consistent between search-map and hi-lock-map Kaushal
2015-07-11 18:50 ` Kaushal
2015-07-11 19:48 ` Juri Linkov
2015-07-11 19:51 ` Kaushal
2015-07-12 7:07 ` Vaidheeswaran C
2015-07-12 13:21 ` Kaushal
2015-07-12 14:48 ` Vaidheeswaran C
2015-07-12 14:48 ` Vaidheeswaran C
2015-07-12 15:15 ` Eli Zaretskii
2015-07-12 15:33 ` Vaidheeswaran C
2015-07-12 16:25 ` Eli Zaretskii
2015-07-12 16:41 ` Kaushal
2015-07-19 7:59 ` Vaidheeswaran C
2015-07-29 2:00 ` Kaushal
2015-07-29 22:31 ` Juri Linkov
2015-07-30 22:48 ` Stefan Monnier [this message]
2015-07-31 1:32 ` Kaushal
2015-08-18 16:22 ` Kaushal
2015-08-19 22:23 ` Juri Linkov
2015-08-20 1:09 ` Kaushal
2016-02-02 20:45 ` Kaushal Modi
2016-02-05 0:54 ` Juri Linkov
2016-02-05 1:48 ` John Wiegley
2016-02-05 17:00 ` Kaushal Modi
2016-02-07 17:57 ` John Wiegley
2016-02-07 19:23 ` Alan Mackenzie
2015-07-15 15:44 ` David Koppelman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsi85clir.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=kaushal.modi@gmail.com \
--cc=vaidheeswaran.chinnaraju@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.