Hi Dudes,

I know this is a little off topic, but I'm stumped and could use some
input.

From my PC I connect to several different hosts. Using the same
method (rexec) and on these hosts I start an xterm window and end up
logged in with the same terminal setting (xterm) and the sessions have
the same values reported from stty -a.

On one of the sessions (a DEC Alpha) my backspace, delete and
history functions perfectly well. On the other (Linux) the backspace and
delete have no effect. (But ^U works). The history display is also
screwed, as it doesn't delete the current line before displaying the prior
line.

Anyone got any ideas?

Martin Bowes
--
Random Duckman Quote #102:
Cornfed: Uh Oh.
Duckman: 'Uh Oh' as in 'Nice Work?'
Cornfed: No, as in 'You're screwed.'

Hi Paul,

Gee its getting dark up here! Daylight savings end soon as well.
Bummer.

I've found out that the backspace and delete do work. But they delete
the characters to the right of the cursor not the ones to the left.

I'm currently trying to find a termcap setting that says something like.
sM: Boolean - screw with Marty
sN: Boolean - sneer when you do it.

Any ideas?

Marty

martin.bowes (AT) ctsu (DOT) ox.ac.uk wrote:
Marty,

Try
TERM=xterm
TERM_INGRES=dgxterm

I've successfully used that in sco, dg and hp installations running
xterms

Good luck....

Hi Karl, Paul et al

Yep. I'm not connected to an Ingres application at all.

All I've done is initiate a connection via rexec (or telnet) from my PC to
a Linux box and I'm running xterm there with the display set to my PC.

As for Ingres terminal mappings...
I connected to accessdb using TERM_INGRES = vt100fx and now all
my function keys are screwed up as well. The backspace and delete
simply print the [3~ and do nothing else....

I tried the TERM_INGRES=dgxterm suggested by 'Oldschool' and that
didn't work either.

I made a terminal mapping for my Xpro keyboard and set
TERM_INGRES=xpro and connected. This at least got the function
keys working again, but the backspace is still [3~.

All of this used to work when I connected to the dec alpha box first and
then just ssh'd over to the linux platform....But the writing is on the wall
for that platform.

My suspicion is that until I can get the OS command line to use
backspace and delete in the normal fashion my Ingres Termcaps could
be stuffed as well.

speed 38400 baud; rows 72; 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


This ahs got 'Long day' written all over it.

Damn that should be 'has' not 'ahs', now you see why I need that
friggen backspace key!

Marty
--
Random Duckman Quote #101:
Duckman: It would be like old times. We can go swimming, and hiking,
and horseback riding.
Cornfed: We never did any of that.
Duckman: I know, I'm reading it off a tampon box behind you.

On Thu, 2006-10-19 at 09:35 +0100, martin.bowes (AT) ctsu (DOT) ox.ac.uk wrote:

What are you using on the PC for an X server?



I'd agree with that.



FWIW that's exactly the output I get on my Fedora Core 4 box - except
for rows which is 24.

What are your xmodmap settings? Try comparing xmodmap -pk for the
working machine with the one that doesn't

If that doesn't help - maybe try a different X server. I use Xming
(http://freedesktop.org/wiki/Xming) when I'm on a Windows machine -
mostly cos it's free and self-contained. Though these days my desktop is
Linux so I've already got an X server running and I tend to use ssh -X
to connect to other linux boxes.

--
Paul Mason
Technical Support Specialist
Ingres

+44 (0) 1753 559538

Hi Paul et al,

Something called HummingBird Exceed.

It came with the PC.

The same.

I'm probably going to have to do something like that. But I'd
rather not just yet. I'm sure there is a simple logical explanation for
this...

Marty

martin.bowes (AT) ctsu (DOT) ox.ac.uk wrote:
< snip >

Hi Marty,

Sorry, I missed the bit about the "command line" earlier.

Let's take this one step at a time.

Exceed works on one (Alpha), not the other (Linux). Issues w/ command
line + Ingres + apps.

I've used Exceed for years (as well as Reflection/X) and its never
missed a beat. The fact that it works one place and not the other
indicates that the problem is that the config at the OS level, or
Xmodmap differ. You've confirmed xmodmap, so your gonna need to dive
into OS keys. I would reserve changing X server for later (if at all)

I've no experience w/ Alphas and limited Linux, mostly DG-UX, SCO,
HP-UX and AIX, but the following may help (they won't hurt).

If both boxes are using terminfo databases, then a good start would be
to compare the output of the definitions. man terminfo, tic (terminfo
compiler), untic (terminfo decompiler) and infocmp.

You might consider copying the terminfo file (/usr/lib/terminfo/x/xterm
?) from the Alpha to the linux box as something like xterm_mb. untic
it, change the alias at the beginning to xterm_mb, recompile it, change
TERM=xterm_mb and seem if that causes the command line to behave
correctly. If it does, set TERM_INGRES to xterm ( or whatever you were
used to on the Alpha ) and see if it wants to play now.

If all of the above works, stash a copy of xterm_mb, and fix your
profile accordingly. (I'd say fix the existing xterm def, but
patches/updates could overwrite it)

Good luck...hth

Scott

OldSchool <scott.myron (AT) fds (DOT) com> wrote:
He might, but it won't work properly (they're different offsets for
the terminal capabilities - some things will work, others won't).

in any case, the terminfo is irrelevant to the question.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

On Oct 20, 12:28 pm, Thomas Dickey <dic... (AT) saltmine (DOT) radix.net> wrote:

Are you saying the problem is w/ termcap then? or something else
totally?

Thx...

OldSchool <scott.myron (AT) fds (DOT) com> wrote:


No - I meant that most of the problems are from the shell versus the terminal
emulator, which isn't getting much data from the terminfo. I don't see the
Linux shell identified but it's likely bash, which uses lots of key assignments
that aren't derived from the terminal description.

Assuming he's really running xterm...

The "delete" key could be the "Delete" from the 6-key editing keypad,
or the "Del" from the numeric keypad. The former is controlled by
a resource setting - man xterm:

deleteIsDEL (class DeleteIsDEL)
Specifies whether the Delete key on the editing keypad should
send DEL (127) or the VT220-style Remove escape sequence. The
default is ``false,'' for the latter.

For backspace - it depends on whether he's expecting it to send an ASCII
BS or DEL. For instance - man xterm:

backarrowKey (class BackarrowKey)
Specifies whether the backarrow key transmits a backspace (8)
or delete (127) character. This corresponds to the DECBKM con-
trol sequence. The default (backspace) is ``true.'' Pressing
the control key toggles this behavior.

(both features can be set via the control/left mouse menu)

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net