From: Steve Goodwin <SteveG@bitscorp.com>
To: linux-c-programming@vger.kernel.org
Subject: RE: Curses and key-up information
Date: Tue, 7 Jan 2003 11:49:49 -0000 [thread overview]
Message-ID: <4DB84F6A7711D511A5020002A550C8B778718F@BELL> (raw)
Thanks for that. A (deeper) trawl provided a post from 6/8/02 (thread: Re:
question about gcc and keyboard hadling) with some source code - will try it
l8r when I'm at a Linux box.
Steev
The information in this Internet Email is confidential and is intended
solely for the addressee. Access, copying or re-use of information in it by
anyone else is unauthorised. Please immediately notify the sender if you are
not the intended recipient and have received this mail.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of Bits Corp plc or any of its affiliates.
Tel. +44 (0)20 8282 7200
Fax. +44 (0)20 8450 9966
next reply other threads:[~2003-01-07 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 11:49 Steve Goodwin [this message]
2003-01-17 0:17 ` Curses and key-up information +RudyMartin
2003-01-17 11:21 ` Jan-Benedict Glaw
-- 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=4DB84F6A7711D511A5020002A550C8B778718F@BELL \
--to=steveg@bitscorp.com \
--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).