From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 29837@debbugs.gnu.org
Subject: bug#29837: UTF-16 char display problems and the macOS "character palette"
Date: Sun, 24 Dec 2017 20:57:04 +0200 [thread overview]
Message-ID: <834logj6nz.fsf@gnu.org> (raw)
In-Reply-To: <20171224182321.GA72021@breton.holly.idiocy.org> (message from Alan Third on Sun, 24 Dec 2017 18:23:21 +0000)
> Date: Sun, 24 Dec 2017 18:23:21 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: 29837@debbugs.gnu.org
>
> > You need to tell Emacs that keyboard input is in UTF-16. Did you try
> > "C-x RET k"?
>
> I have now but I can’t find a utf-16 option that is ‘suitable’ for
> keyboard input.
What do you mean by "option" and by "suitable"?
next prev parent reply other threads:[~2017-12-24 18:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 16:00 bug#29837: UTF-16 char display problems and the macOS "character palette" Alan Third
2017-12-24 16:56 ` Eli Zaretskii
2017-12-24 18:23 ` Alan Third
2017-12-24 18:57 ` Eli Zaretskii [this message]
2017-12-24 19:28 ` Alan Third
2017-12-24 19:34 ` Eli Zaretskii
2017-12-25 20:13 ` Philipp Stephani
2017-12-25 21:01 ` [PATCH] Allow inserting non-BMP characters Philipp Stephani
2017-12-26 1:26 ` Alan Third
2017-12-26 4:46 ` Eli Zaretskii
2017-12-26 10:35 ` Philipp Stephani
2017-12-26 16:11 ` Eli Zaretskii
2017-12-26 18:50 ` Philipp Stephani
2017-12-26 20:22 ` Eli Zaretskii
2017-12-26 21:36 ` Alan Third
2017-12-27 3:41 ` Eli Zaretskii
2017-12-28 11:38 ` Alan Third
2017-12-28 12:31 ` Philipp Stephani
2017-12-28 16:29 ` Eli Zaretskii
2017-12-29 20:14 ` Philipp Stephani
2017-12-29 20:27 ` Eli Zaretskii
2018-01-07 15:51 ` Philipp Stephani
2018-01-07 17:40 ` Eli Zaretskii
2018-01-07 18:44 ` Philipp Stephani
2017-12-25 21:07 ` bug#29837: UTF-16 char display problems and the macOS "character palette" Philipp Stephani
2017-12-26 1:34 ` Alan Third
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=834logj6nz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29837@debbugs.gnu.org \
--cc=alan@idiocy.org \
/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.