unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master c9cb59b 2/2: * etc/TODO: Entry about converting to defvar-keymap.
Date: Fri, 10 Dec 2021 22:20:20 -0800	[thread overview]
Message-ID: <CADwFkmmPbdD5SHuWYYCkj35d4BFe=u0b+dpmcc-MeoQxzHa=4g@mail.gmail.com> (raw)
In-Reply-To: <87zgp7x2qq.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 2) The temptation to rewrite a map when doing adding a key or two is
> great, but it makes that single commit harder to read.  So converting
> maps as a separate commit makes things easier to read, not harder.

Agreed.

(IMHO, often it is better to first make the cleanup, and then the
logical change in a separate commit.  My impression is that this style
is not often used in Emacs development.)

> While doing conversion to defvar-keymap, we'd also convert to #', which
> gives us byte compilation support for mis-spelled commands.  I found a
> couple of bindings that pointed to commands that doesn't exist when
> doing the few conversions that I've done.

In addition to this, and keeping in mind also the other points you make,
I think getting some experience with defvar-keymap will help stabilize
and work out any problems in its interface well in advance of Emacs 29.

For example, Bug#52374 was found by me poking at the keymaps in
re-builder.el.  Although presumably that bug would have been eventually
been found anyways, it's always nice to discover such things early.
I have the feeling that there might exist more bugs and opportunities
for improvement that we haven't yet noticed.



  reply	other threads:[~2021-12-11  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 15:00 master c9cb59b 2/2: * etc/TODO: Entry about converting to defvar-keymap Eli Zaretskii
2021-12-10 15:37 ` Stefan Kangas
2021-12-10 16:51   ` Eli Zaretskii
2021-12-11  3:02     ` Lars Ingebrigtsen
2021-12-11  6:20       ` Stefan Kangas [this message]
2021-12-10 15:59 ` dick
2021-12-10 16:44   ` Alan Mackenzie
2021-12-11  0:56   ` Po Lu

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='CADwFkmmPbdD5SHuWYYCkj35d4BFe=u0b+dpmcc-MeoQxzHa=4g@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    /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).