From: "Quang Nguyen (Ngo)" <quang@tapeware.com>
To: Varun Kacholia <varunk@cse.iitb.ac.in>, gcc-help@gcc.gnu.org
Subject: Re: keyboard events
Date: Wed, 28 Aug 2002 08:54:00 -0000 [thread overview]
Message-ID: <200208280854.49981.quang@tapeware.com> (raw)
In-Reply-To: <20020828181549.B1340@voxel.cse.iitb.ac.in>
On Wednesday 28 August 2002 12:42 pm, Varun Kacholia wrote:
> hello
> I wanted to know whether gcc provides some facility to get the various
> keyboard events like KEY_DOWN/KEY_UP etc.
> If not then what would be the best way to avail them
> I am using gcc3 on redhat 7.2 .
> thanks for any help
gcc is just a compiler. You want to read the man page of ncurses (man
ncurses).
--
Quang
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
prev parent reply other threads:[~2002-08-28 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 5:42 Varun Kacholia
2002-08-28 7:50 ` John Love-Jensen
2002-08-28 8:54 ` Quang Nguyen (Ngo) [this message]
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=200208280854.49981.quang@tapeware.com \
--to=quang@tapeware.com \
--cc=gcc-help@gcc.gnu.org \
--cc=varunk@cse.iitb.ac.in \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).