From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Screwed up keyboard mappings on RedHat
Date: Fri, 18 Apr 2003 20:47:12 +0200 [thread overview]
Message-ID: <84of33d4nj.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: roy-1E7FB8.12120518042003@reader1.panix.com
Roy Smith <roy@panix.com> writes:
> Hmmm. It's currently set to "t". It looks like that might be what I
> need to play with, thanks.
>
> In the meantime (before your response came), I had already discovered
> keyboard translation tables and fixed the problem with:
>
> (keyboard-translate ?\C-h nil)
> (keyboard-translate ?\C-? nil)
Right. That's basically the effect of
(normal-erase-is-backspace-mode -1) :-)
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
prev parent reply other threads:[~2003-04-18 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 14:26 Screwed up keyboard mappings on RedHat Roy Smith
2003-04-18 15:28 ` Kai Großjohann
2003-04-18 16:12 ` Roy Smith
2003-04-18 18:12 ` Kevin Rodgers
2003-04-21 16:50 ` Kevin Rodgers
2003-04-18 18:47 ` Kai Großjohann [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84of33d4nj.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).