Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

xterm backspace problem on Red Hat 8.0 server

Status
Not open for further replies.

jjwood64

IS-IT--Management
Mar 3, 2002
7
0
0
US
Hi, folks.

As the subject says, I recently built and patched
a Red Hat 8.0 server. However, I've ran into a problem,
as I am in an environment where users access these
Red Hat servers via Exceed software. Normally, the
user will bring up a window via telnet, then run
xterm, then work within that xterm window.

The problem is whenever the user commits a typo
and has to use the backspace key, the user winds
up typing the ~ character instead. I've looked
at /etc/X11/XF86Config and looked at /etc/termcap
and have tried & hacked various things to no
avail. However, when this user uses a korn shell,
xterm works fine; but because we use .cshrc, this
is not an option.

I am suspecting the problem could be with
the ENV setup, but I've looked at redhat.com
and cannot find a good answer. Does anyone
have any ideas? I thank you kindly
in advance.
 
inside of the exceed setup, change the keyboard to
"backspace sends delete".

Its been a long time since i've used exceed, if anyone can give more specific intructions, please post.

 
lvennard is correct. Same thing happens with Putty.
SHIFT-BACKSPACE will work.
There should be a Keyboard setting in the Terminal Configuration.

 
Thank you for the replies. I have looked at the
Exceed side this morning, but I still wind up with
the same results.:-(
 
You can fudge this a little by using the stty erase command. Basically just type 'stty erase ' then press the backspace key then return. Hopefully you should then find that backspace operates normally. If this works, logout, log back in and edit .cshrc and add the command (the backspace should still give the incorrect character at this point).

Scotty
 
stty erase works when you edit a file in vi. From the command line, though, I still produce the error:

lonlin2{jwood}51: asdsadasdas~~~~~~~~~~~~~
asdsadasdas~~~~~~~~~~~~~: Command not found.
lonlin2{jwood}52: asdsadasad~
asdsadasad~: Command not found.
lonlin2{jwood}53: stty erase '^'
lonlin2{jwood}54: asdsadas~~~~
asdsadas~~~~: Command not found.
 
Now I am a little confused.... did the backspace produce a '^' on the stty erase line, but '~' on the others? The only reason I ask is that the '^' usually indicates a control character i.e. I have redhat on my laptop that I am using at the moment and my settings are as follows:

[scott@holly work]$ stty -a
speed 38400 baud; rows 40; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;


So my erase is set to CONTROL+? - you seem to have set your erase to just CONTROL...

Sorry I haven't helped much in this post...

Scotty
 
Scotty, thank you for replying.

When I tried &quot;stty erase <backspace>&quot;, I would receive
the result &quot;stty: missing argument for erase.&quot; So, from my original Terminal window, the backspace is fine on the
command prompt.

I tried the following below, then started an xterm:

lonlin4{jwood}55: stty -a
speed 9600 baud; rows 64; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

lonlin4{jwood}56: stty erase '^?'

lonlin4{jwood}57: stty -a
speed 9600 baud; rows 64; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

lonlin4{jwood}58: xterm


The xterm window pops up, but when shecking stty -a,
I receive the same info from my first stty check:

lonlin4{jwood}51: stty -a
speed 38400 baud; rows 24; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^; kill = ^U; eof = ^D; eol = <undef>;
eol2 = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W;
lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt
echoctl echoke

So, how do I set the NOCONTROL portion properly, Scott? Thank you kindly in advance.

 
I am using redhat 8 and receiving the same problem with exceed? Did anyone find a resolution?
 
Try adding the following line to your .Xdefaults file:
XTerm*VT100.translations: #override \n\ <Key>Delete: string(0x7f)

Hope this helps,

Bruce
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top