From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: emacs-28 56026242e4: Explain how to bind keys to non-ASCII sequences
Date: Tue, 15 Nov 2022 10:14:28 +0100 [thread overview]
Message-ID: <871qq4eg0b.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmnqt_2pgkiL7i98zuTRhLqkQWq9N6U2n+FAHNjRYqZSCQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 15 Nov 2022 01:09:56 -0800")
>>>>> On Tue, 15 Nov 2022 01:09:56 -0800, Stefan Kangas <stefankangas@gmail.com> said:
Stefan> Robert Pluim <rpluim@gmail.com> writes:
>>>>>>> On Mon, 14 Nov 2022 19:40:35 -0800, Stefan Kangas <stefankangas@gmail.com> said:
>>
Stefan> This section has changed quite a bit on master, including using
Stefan> `keymap-global-set' instead. Unfortunately, I'm not sure what if
Stefan> anything needs adding to the text already on master. Could you please
Stefan> look into it, or even help merge it?
>>
>> Well this has opened a can of worms:
Stefan> Indeed. I guess there are several issues to discuss or resolve here.
Stefan> Meanwhile, in the interest of being able to merge the emacs-28 branch at
Stefan> all, is it okay if we just skip the changes you made while we work on a
Stefan> new patch for master?
Yes, thatʼs probably best. Perhaps I should now stop making my doc
changes on emacs-28 first 😀
Once we resolve this I can redo the patch for master.
Robert
--
next prev parent reply other threads:[~2022-11-15 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166844275725.4187.2343107623845911514@vcs2.savannah.gnu.org>
[not found] ` <20221114161917.7FC8AC00AB5@vcs2.savannah.gnu.org>
2022-11-15 3:40 ` emacs-28 56026242e4: Explain how to bind keys to non-ASCII sequences Stefan Kangas
2022-11-15 8:28 ` Robert Pluim
2022-11-15 9:09 ` Stefan Kangas
2022-11-15 9:14 ` Robert Pluim [this message]
2022-11-16 7:44 ` Stefan Kangas
2022-11-16 8:50 ` Robert Pluim
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=871qq4eg0b.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--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).