From: BurnZeZ@feline.systems
To: 9front@9front.org
Subject: Re: [9front] drawterm qid re-use
Date: Tue, 23 Feb 2016 04:30:42 -0500 [thread overview]
Message-ID: <40d0b5ff5355b132773548117d901cc1@meiling.znet> (raw)
In-Reply-To: <44542a1f5e907affffce7422fb84df25@felloff.net>
After disregarding the comment at drawterm/gui-x11/x11.c:/polling/
and changing XA_STRING to utf8string in the following couple lines
to allow for utf8 clipboard shennanigans, I find this iteration of
drawterm quite usable.
I did a bit of playing around and haven't noticed any bugs so far.
Also, do you know off-hand which changes would have dramatically
increased the speed of /mnt/term/* filesystem interaction?
next prev parent reply other threads:[~2016-02-23 9:30 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 [this message]
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
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=40d0b5ff5355b132773548117d901cc1@meiling.znet \
--to=burnzez@feline.systems \
--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).