From: Jeremy Bryant via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: "प्रद्युम्न परांजपे" <pradyparanjpe@gmail.com>,
"Justin Burkett" <justin@burkett.cc>,
71718@debbugs.gnu.org
Subject: bug#71718: Unicode symbols to represent which key special keys, bug#71718: Unicode symbols to represent which key special keys
Date: Fri, 28 Jun 2024 18:59:19 +0100 [thread overview]
Message-ID: <87o77lhrt4.fsf@jeremybryant.net> (raw)
In-Reply-To: <87bk3la52g.fsf@gmail.com> (Robert Pluim's message of "Fri, 28 Jun 2024 09:40:07 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Fri, 28 Jun 2024 11:43:58 +0530, प्रद्युम्न परांजपे <pradyparanjpe@gmail.com> said:
>
> Prady> I am unaware of the protocol here.
> Prady> I submitted the PR as a bug as advised by the owner of the repository on
> Prady> github.
>
> Prady> I agree with, and accept both suggestions (from Robert and Jeremy).
> Prady> How do I proceed with including the suggestions?
>
> Change your code to match the suggestions, ensure that all the changes
> are in 1 commit, then reply to this email with the file produced by
>
> git format-patch -1
>
> as an attachment. See "** Getting involved with development" in
> CONTRIBUTE in the emacs sources for more info.
>
> Prady> I am afraid I, being ignorant, might end up opening multiple bug reports
> Prady> messing up things.
> Prady> So I am not actively doing anything right now.
> Prady> Please guide me through.
>
> As long as you just reply to '71718@debbugs.gnu.org' and the other
> people in the email headers, you wonʼt end up creating multiple
> reports.
>
> Robert
Indeed.
Prady, to explain the recent change, please note that the original repo was archived on github,
recently on the 25th, just after your initial PR.
which-key is now developed as part of Emacs, so please continue to
submit patches and bug reports here.
prev parent reply other threads:[~2024-06-28 17:59 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
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 [this message]
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=87o77lhrt4.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 \
--cc=rpluim@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).