From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Keymap initialization
Date: Mon, 26 Jun 2017 18:08:07 +0000 [thread overview]
Message-ID: <20170626180807.GC2471@acm> (raw)
In-Reply-To: <jwv37am7j3v.fsf-monnier+emacsdiffs@gnu.org>
Hello, Stefan.
On Mon, Jun 26, 2017 at 13:41:50 -0400, Stefan Monnier wrote:
> >> This is anti-idiomatic: Emacs's own code has been making the
> >> opposite change over the years in most/all bundled packages.
> > I got sick and tired of having to do M-: (makunbound 'foo-map) before
> > loading files with changed keymaps. As a developer yourself, you should
> > welcome such changes.
> C-M-x on the (defvar foo-map ...) takes care of it as well. Or using
> `defconst` instead of `defvar` would do the trick also (although that's
> also less idiomatic). Or write a new M-x reload-file which causes all
> the defvars to be re-evaluated.
Workarounds, every one.
> >> I consider indispensable, but I really don't see why CC-mode's keymaps
> >> need to behave differently from all other major modes.
> > They don't.
> Obviously they do, which is why you made the change.
> > Precisely how these keymaps are constructed and loaded is of
> > lesser importance.
> It seems important enough for you to change from the idiomatic form to
> a non-idiomatic one.
<sigh>. It's of near zero importance to the Emacs team, it's of quite
some importance to the hacker who's currently changing the key maps.
> But yes, I do think it's of lesser importance, which is why I think it's
> more important that the downsides (e.g. the need to C-M-x or (makunbound
> 'foo-map), or the need to re-run your .emacs after reloading cc-mode.el,
> ...) be standardized.
Why do you think things should be standardised? (Not a rhetorical
question)
> IOW, rather than make CC-mode yet-a-bit-more different from the rest of
> Emacs, I wish you would try to find a way to solve your problem globally.
> If this annoyance affects you, there's a good chance it affects many
> other developers, so finding a general solution would be a lot better.
That seems to presume that the way things are already done in Emacs is
at or near some optimum, and deviating from that way is therefore
sub-optimal. I don't think there's any evidence for this. I see some
"standard" ways of doing things in Emacs which I don't think are good.
People should feel free to try out various ways of doing things. Only
this way can new ideas come forth, leading to a gradual improvement in
Emacs when these ideas spread.
Setting key map entries at load time could be a general solution to that
particular annoyance. People, having seen it in CC Mode, will be able
to adapt it for their own modes, should they see fit.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2017-06-26 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170615210438.18512.16715@vcs0.savannah.gnu.org>
[not found] ` <20170615210440.2D57C206CD@vcs0.savannah.gnu.org>
2017-06-25 21:29 ` Keymap initialization (was: [Emacs-diffs] master 7a2038d: Create a toggle between block and line comments in CC Mode) Stefan Monnier
2017-06-26 16:39 ` Alan Mackenzie
2017-06-26 17:41 ` Keymap initialization Stefan Monnier
2017-06-26 18:08 ` Alan Mackenzie [this message]
2017-06-26 20:27 ` Stefan Monnier
2017-06-26 21:13 ` Alan Mackenzie
2017-06-27 2:34 ` Stefan Monnier
2017-06-26 20:08 ` Clément Pit-Claudel
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=20170626180807.GC2471@acm \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).