From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Adam Porter <adam@alphapapa.net>, emacs-devel@gnu.org
Subject: Re: Suggestion for improving ergonomics of repeat-maps: define-repeat-map
Date: Mon, 04 Oct 2021 21:18:35 +0300 [thread overview]
Message-ID: <875yuc7hzo.fsf@mail.linkov.net> (raw)
In-Reply-To: <87fsthnmpv.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 04 Oct 2021 11:49:48 +0200")
> But I guess it's a bit confusing how the syntaxes are similar but
> different? I went back and forth a number of time on the syntax --
> define-keymap is a function, so it can't do the function-line macro
> syntax that defvar-keymap can (which is better). But having the first
> argument of define-keymap be a list (which would be preferable in most
> ways) just looked awkward.
>
> (define-keymap (list :full t)
> ...)
>
> But I'm open to changing it if it's too confusing the way it is now.
But why not to unify them in another direction, i.e. not to use a list
for options in defvar-keymap. Then both syntaxes would be the same:
(define-keymap
:full t
"g" #'eww-reload)
(defvar-keymap eww-textarea-map
:full t
"g" #'eww-reload)
instead of
(defvar-keymap eww-textarea-map
(:full t)
"g" #'eww-reload)
next prev parent reply other threads:[~2021-10-04 18:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 3:22 Suggestion for improving ergonomics of repeat-maps: define-repeat-map acdw
2021-09-08 14:54 ` Philip Kaludercic
2021-09-08 17:01 ` acdw
2021-09-09 17:50 ` Juri Linkov
2021-09-09 18:06 ` Lars Ingebrigtsen
2021-09-09 20:35 ` Augusto Stoffel
2021-09-09 20:39 ` Lars Ingebrigtsen
2021-09-10 0:53 ` acdw
2021-09-10 10:53 ` Lars Ingebrigtsen
2021-10-04 8:22 ` Lars Ingebrigtsen
2021-10-04 9:05 ` Adam Porter
2021-10-04 9:49 ` Lars Ingebrigtsen
2021-10-04 11:29 ` Adam Porter
2021-10-04 11:33 ` Lars Ingebrigtsen
2021-10-04 18:18 ` Juri Linkov [this message]
2021-10-04 19:02 ` Lars Ingebrigtsen
2021-10-04 19:24 ` Stefan Monnier
2021-10-04 19:54 ` Lars Ingebrigtsen
2021-10-04 20:16 ` Lars Ingebrigtsen
2021-09-10 0:53 ` acdw
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=875yuc7hzo.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=adam@alphapapa.net \
--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).