From: Robert Pluim <rpluim@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Proper way to add bindings under C-x 8
Date: Tue, 30 Nov 2021 13:39:08 +0100 [thread overview]
Message-ID: <87k0gp4y37.fsf@gmail.com> (raw)
In-Reply-To: <87lf15ev23.fsf@web.de> (Michael Heerdegen's message of "Tue, 30 Nov 2021 12:34:28 +0100")
>>>>> On Tue, 30 Nov 2021 12:34:28 +0100, Michael Heerdegen <michael_heerdegen@web.de> said:
Michael> Howard Melman <hmelman@gmail.com> writes:
>> I assume this is because these emoji use some more
>> complicated encoding since C-x = tells me it's a composed
>> form unlike the others. Is there a way to include these as
>> well? I don't really want to have to know the different way
>> different emoji are encoded but if necessary I can.
Michael> I don't know anything about it. But I can see that these card emojis
Michael> are not characters - wrapped into a string you get a length of 2:
Michael> (length "♠️") ==> 2
Michael> Inserting the two consecutive characters seems to work:
Michael> (insert ?♠ 65039) ;; inserts ♠️
Michael> So iso-transl-define-keys doesn't seem to be usable for this task
Michael> indeed.
I think youʼre right. Using the global map works fine if you use the
syntax
[?♠?️]
(where thereʼs a literal U+FE0F after that second "?")
but with the iso-transl-ctl-x-8-map it always inserts only the last
element of that vector.
Robert
--
next prev parent reply other threads:[~2021-11-30 12:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 16:57 Proper way to add bindings under C-x 8 Howard Melman
2021-04-10 17:41 ` Eli Zaretskii
2021-04-10 21:35 ` Howard Melman
2021-04-11 6:45 ` Eli Zaretskii
2021-11-29 16:21 ` Howard Melman
2021-11-30 11:34 ` Michael Heerdegen
2021-11-30 12:39 ` Robert Pluim [this message]
2021-11-30 13:07 ` Michael Heerdegen
2021-11-30 13:39 ` Robert Pluim
2021-11-30 16:32 ` Howard Melman
2021-11-30 16:49 ` Robert Pluim
2021-11-30 17:25 ` Eli Zaretskii
2021-11-30 17:39 ` Robert Pluim
2021-11-30 17:43 ` Howard Melman
2021-12-02 10:26 ` Robert Pluim
2021-12-02 14:44 ` Michael Heerdegen
2021-12-02 15:03 ` Robert Pluim
2021-12-02 15:27 ` Michael Heerdegen
2021-12-02 15:56 ` Robert Pluim
2021-12-02 16:18 ` Michael Heerdegen
2021-12-02 16:48 ` Robert Pluim
2021-11-30 16:43 ` Robert Pluim
2021-11-30 17:29 ` Howard Melman
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=87k0gp4y37.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).