From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] drawterm qid re-use
Date: Wed, 24 Feb 2016 13:38:15 -0500 [thread overview]
Message-ID: <79fe234876ca7a560f1426338ef6a16e@ghost.sfldmibb02.det.wayport.net> (raw)
In-Reply-To: <bb54cb79fb7c1e3d36345ce592f3923a@meiling.znet>
> Previously, copying unicode from X11 to drawterm resulted in unescaped
> unicode ('┱' becomes '\u2531'), or occasionally mangled byte sequences.
Confirmed, I observed this many times.
sl
next prev parent reply other threads:[~2016-02-24 18:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 7:45 BurnZeZ
2016-02-23 7:46 ` [9front] " cinap_lenrek
2016-02-23 9:30 ` BurnZeZ
2016-02-23 14:39 ` cinap_lenrek
2016-02-23 20:57 ` BurnZeZ
2016-02-23 22:47 ` cinap_lenrek
2016-02-24 10:30 ` cinap_lenrek
2016-02-24 18:30 ` BurnZeZ
2016-02-24 18:38 ` sl [this message]
2016-02-23 13:27 ` kokamoto
2016-02-23 14:02 ` hiro
2016-02-23 14:31 ` cinap_lenrek
2016-02-24 0:22 ` kokamoto
2016-02-23 14:35 ` sl
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=79fe234876ca7a560f1426338ef6a16e@ghost.sfldmibb02.det.wayport.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.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.
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).