all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "प्रद्युम्न परांजपे" <pradyparanjpe@gmail.com>
Cc: Justin Burkett <justin@burkett.cc>, 71718@debbugs.gnu.org
Subject: bug#71718: Unicode symbols to represent which key special keys
Date: Sat, 22 Jun 2024 19:17:25 +0100	[thread overview]
Message-ID: <87iky03kqy.fsf@jeremybryant.net> (raw)
In-Reply-To: <CABt=8OY9KzzvpYxXbzH1mKnGPQKWQ4BQB1ekCnubdzdwrBb==w@mail.gmail.com> ("प्रद्युम्न परांजपे"'s message of "Sat, 22 Jun 2024 14:31:15 +0530")

प्रद्युम्न परांजपे <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.

> 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'.





  reply	other threads:[~2024-06-22 18:17 UTC|newest]

Thread overview: 6+ 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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iky03kqy.fsf@jeremybryant.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71718@debbugs.gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=justin@burkett.cc \
    --cc=pradyparanjpe@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 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.