From: Mauro Aranda <maurooaranda@gmail.com>
To: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: emacs-devel@gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: Re: Proposal to add Popper to ELPA
Date: Fri, 8 Sep 2023 21:33:17 -0300 [thread overview]
Message-ID: <c4cd433c-21bb-efa6-987f-8718d525cfe5@gmail.com> (raw)
In-Reply-To: <87msxwib82.fsf@gmail.com>
On 8/9/23 18:52, Karthik Chikmagalur wrote:
>> One more point, the user option `popper-echo-dispatch-keys' seems to
>> have a broken type. Shouldn't it be something like
>>
>> (repeat (choice key-sequence character))
>>
>> with proper tag annotations?
>
> I'm not sure it makes sense to enter these keybindings one-by-one, or to
> have tags attached to each entry. The idea is that this is a list of
> keys that will be bound to buffers.
>
> I will change it from (group string character) to (group key-sequence
character).
>
Did you see my message about popper-echo.el? Here is a link to the
archives:
https://lists.gnu.org/archive/html/emacs-devel/2023-09/msg00438.html
I don't think is recommended to use the key-sequence type. It was
declared obsolete in favor of a key type. But the key type isn't
available on Emacs 26.1, so that's why I proposed to keep the character
and string types.
next prev parent reply other threads:[~2023-09-09 0:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 16:55 Proposal to add Popper to ELPA Karthik Chikmagalur
2023-09-05 17:38 ` Philip Kaludercic
2023-09-05 20:12 ` Karthik Chikmagalur
2023-09-05 20:37 ` Mauro Aranda
2023-09-06 17:36 ` Philip Kaludercic
2023-09-06 23:09 ` Karthik Chikmagalur
2023-09-05 20:27 ` Mauro Aranda
2023-09-05 20:49 ` Karthik Chikmagalur
2023-09-05 21:05 ` Mauro Aranda
2023-09-06 17:13 ` Karthik Chikmagalur
2023-09-08 17:25 ` Philip Kaludercic
2023-09-08 21:52 ` Karthik Chikmagalur
2023-09-09 0:33 ` Mauro Aranda [this message]
2023-09-09 0:57 ` Karthik Chikmagalur
2023-09-09 8:10 ` Philip Kaludercic
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=c4cd433c-21bb-efa6-987f-8718d525cfe5@gmail.com \
--to=maurooaranda@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=karthikchikmagalur@gmail.com \
--cc=philipk@posteo.net \
/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.