To: 9fans <firstname.lastname@example.org>
Subject: [9fans] Re: Panic with 'compose-x' input
Date: Sun, 12 Feb 2023 12:21:14 -0500 [thread overview]
Message-ID: <16762224740.C4cC2cBB.email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
I forgot about Runemax, better to use it instead of 0x10ffff.
Just to be clear, without this entering a unicode character represented by more than 4 runes (compose key, then x key) will produce a system panic. This thing has been boring me for a while by accident, I didn't imagine this was the cause.
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1097 bytes --]
prev parent reply other threads:[~2023-02-12 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 5:29 [9fans] " adr
2023-02-12 17:21 ` adr [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).