From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] keyboard(6) lies
Date: Tue, 18 Feb 2014 10:12:39 +0100 [thread overview]
Message-ID: <bd71d7f7cbb9e3a76be70f455eb6ff4b@felloff.net> (raw)
In-Reply-To: <6231b699a28c597aeb29c262c748fdbb@utsuho.znet>
kbdfs is not involved when you use drawterm. /dev/cons, /dev/mouse and
/dev/draw and all that stuff is done by drawterm. (its a fileserver!)
drawterm doesnt provide /dev/kbd. no playing doom for you under drawterm.
rio has a fallback so it can run without a /dev/kbd.
if you want to change compose sequence handling, you'd have to hack drawterm.
--
cinap
next prev parent reply other threads:[~2014-02-18 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 8:19 Ethan Grammatikidis
2014-02-16 16:49 ` [9front] " cinap_lenrek
2014-02-18 8:56 ` brz-systemd-dev
2014-02-18 9:12 ` cinap_lenrek [this message]
2014-02-18 22:21 ` Nick Owens
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=bd71d7f7cbb9e3a76be70f455eb6ff4b@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).