From: Justin Burkett <justin@burkett.cc>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "प्रद्युम्न परांजपे" <pradyparanjpe@gmail.com>,
"Jeremy Bryant" <jb@jeremybryant.net>,
71718@debbugs.gnu.org
Subject: bug#71718: Unicode symbols to represent which key special keys
Date: Fri, 27 Dec 2024 08:48:07 -0500 [thread overview]
Message-ID: <CAF8XuLjygy+Sh3AMQ91OdwpRbigMRE7LCuoM0ct74fzTo4-4Qw@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmn-8LowOXqPzCgNBbA9scZ1hoESUbE2_nFvsWe9_rhcjQ@mail.gmail.com>
On Mon, Dec 23, 2024 at 10:00 PM Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Jeremy Bryant <jb@jeremybryant.net> writes:
>
> > प्रद्युम्न परांजपे <pradyparanjpe@gmail.com> writes:
> >
> >> Tags: patch
> >>
> >> This patch corresponds to the pull request #372
> >> <https://github.com/justbur/emacs-which-key/pull/372>.
> >
> > Adding Justin as the author of which-key. I see from the discussion it
> > was requested to be moved to this bug tracker, so he is aware.
>
> Ping! Justin, any comments on this patch?
It looks ok to me. This is one I had planned on accepting once the
paperwork went through.
Justin
>
> >> This is a proposed feature enhancement in which-key to allow
> >> propertized special key: a single user-defined unicode character that
> >> will replace special keys such as SPC, TAB, RET, ESC, DEL, backspace,
> >> ...
> >>
> >> Commit:
> >>
> >> Unicode symbols to represent which key special keys
> >>
> >> * lisp/which-key.el (which-key-speical-keys):Use
> >
> > There is a typo above in the commit message `special-keys'.
next prev parent reply other threads:[~2024-12-27 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 9:01 bug#71718: Unicode symbols to represent which key special keys प्रद्युम्न परांजपे
2024-06-22 18:17 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-24 3:00 ` Stefan Kangas
2024-12-27 13:48 ` Justin Burkett [this message]
2024-06-23 15:29 ` bug#71718: Unicode symbols to represent which key special keys, " Robert Pluim
2024-06-28 6:13 ` प्रद्युम्न परांजपे
2024-06-28 7:40 ` Robert Pluim
2024-06-28 17:59 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CAF8XuLjygy+Sh3AMQ91OdwpRbigMRE7LCuoM0ct74fzTo4-4Qw@mail.gmail.com \
--to=justin@burkett.cc \
--cc=71718@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
--cc=pradyparanjpe@gmail.com \
--cc=stefankangas@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 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).