From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Curses and key-up information
Date: Fri, 17 Jan 2003 12:21:40 +0100 [thread overview]
Message-ID: <20030117112140.GB9407@lug-owl.de> (raw)
In-Reply-To: <001d01c2bdbd$d746b880$28d831c8@oemcomputer>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
On Thu, 2003-01-16 21:17:36 -0300, +RudyMartin <rmb@coopenet.com.ar>
wrote in message <001d01c2bdbd$d746b880$28d831c8@oemcomputer>:
>
> perhaps its my lack of experience in linux programming but I tried the
> referred source code and it didnt worked
Then you probably did something wrong:-)
> also, the ioctrl documentation says the keyboard access is done trhough the
> tty driver but i wanted a direct keyboard access, like VMware under X
Well, if you do direct I/O the the keyboard controller, you face a
number of problems:
1. Your code is not portable, in no way. Not even between
different architectures running Linux
2. You face races between your code and the in-kernel code which
will cause spurious errors
> since im doing a Brief emulation I was forced to remap some default keys. :(
> (btw the text editor is currently at 5% of completion but its working pretty
> good, if anyone wants a copy of the sources just let me know)
That's not good at all:-(
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-17 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 11:49 Curses and key-up information Steve Goodwin
2003-01-17 0:17 ` +RudyMartin
2003-01-17 11:21 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 14:29 Steve Goodwin
2003-01-06 16:00 ` Glynn Clements
2003-01-07 7:08 ` Jan-Benedict Glaw
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=20030117112140.GB9407@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-c-programming@vger.kernel.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).