Bug 23654 – dvorak keyboard layout backspace problem w/xterm

Bug 23654 - dvorak keyboard layout backspace problem w/xterm

Summary:	dvorak keyboard layout backspace problem w/xterm

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	XFree86 (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mike A. Harris
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-09 11:07 EST by Kevin L. Mitchell
Modified:	2007-04-18 12:30 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-02-06 15:56:11 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Kevin L. Mitchell 2001-01-09 11:07:00 EST

I just installed RedHat 7.0 and set about configuring it and was stymied by
what
appeared to be a problem with xterm.  Whenever I pressed backspace, the
code
submitted to xterm was (from memory) ^[[3~, which of course doesn't do
anything
useful.  So I began working through the xterm manpage to find if there's a
resource
that could be the problem.  No luck.  Then I switched the XkbLayout back to
"us",
and lo and behold, it worked.  Further investigation revealed that the key
symbols
associated with <BKSP> in /usr/X11R6/lib/X11/xkb/symbols/dvorak did not
match
those used by /usr/X11R6/lib/X11/xkb/symbols/us--the dvorak key symbols
were "BackSpace, Delete", whereas the us key symbols were just "BackSpace".
Changing the symbols in the dvorak map fixed the xterm problem.

Comment 1 Eido Inoue 2001-08-24 18:38:57 EDT

I use a dvorak (soft mapped Happy Hacking) on the 7.0 and 7.1. I can't seem to
reproduce your problem.

Note You need to log in before you can comment on or make changes to this bug.