Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 93802 - shift behaves like ctrl in xterm when TERM=xterm
Summary: shift behaves like ctrl in xterm when TERM=xterm
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Seemant Kulleen (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-24 06:31 UTC by Eugene Pavlovsky
Modified: 2005-06-08 05:30 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Pavlovsky 2005-05-24 06:31:27 UTC
I've got a problem with xterm. When I use my text editor (le) in console
(TERM=linux), shift-home and shift-end select to the
beginning/end of the line respectively, while ctrl-home/end go to the
beginning/end of the file. Also, shift-left/right extend the current selection
to the left/right, and ctrl-left/right goes to previous/next word. Now, that's
great. But when I run xterm (TERM=xterm), shift-home/end start to warp me to the
beginning/end of file, shift-left/right move to prev/next word. That is, shift
starts to behave like control. If I change my TERM to linux, home/end (without
modifiers) cease to work at all - no good as well, but shift-home/end start to
work as they should.

The xorg-x11 is 6.8.2-r2 (IIRC), xterm is 202-r1 (IIRC). I tried the 'xterm'
terminfo file from my other linux (slackware) system, where there are no such
problems, and it doesn't change anything.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Thomas Dickey 2005-05-27 16:40:10 UTC
xterm's behavior in this area has been documented since patch #167
and #94, and probably predates anything that Linux console does
with modifiers.  From my point of view, it's an issue with the
Linux console.
Comment 2 Eugene Pavlovsky 2005-05-30 01:30:07 UTC
i seem to get the same behaviour in rvxt-unicode with TERM=rxvt-unicode :(
any idea how to fix it? 
Comment 3 Eugene Pavlovsky 2005-06-08 05:30:31 UTC
is not an xterm issue