From: covici@ccs.covici.com (John Covici)
To: blinux-list@redhat.com
Subject: problems with the keyboard under Linux
Date: Mon, 06 Jul 1998 02:22:19 -0400 [thread overview]
Message-ID: <35a06e2d.ccs@ccs.covici.com> (raw)
Message-ID: <b0Go10r1J8Yb089yn@ccs.covici.com> (raw)
Hi. I am having some weird problems with the keyboard under Redhat
Linux -- particularly when using emacs.
These happen even if there is no version of screen running.
There seems no way to type the controlkey and a function key
simultaneously -- for example if I try control-h followed by c and
then type control-f6, it acts as though I had typed the f6 key itself.
Also, the same thing happens with control right arrow and left arrow
from either keypad.
Is there anyway I can change the key tables to fix this problem? I
did try a couple of things, but the results were even worse than
before.
Any assistance would be appreciated.
--
John Covici
covici@ccs.covici.com
next reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b0Go10r1J8Yb089yn@ccs.covici.com>
` John Covici [this message]
` wlestes
[not found] ` <2JTo10r1JckO089yn@ccs.covici.com>
` John Covici
` wlestes
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=35a06e2d.ccs@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=blinux-list@redhat.com \
/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).