Re: tlug: Kterm/Xterm remote windows config

[Scott Stone <sstone@example.com>]

On Tue, 13 Oct 1998, Frank Bennett wrote:

> 
> I am badly stumped by a Kterm problem.  I _think_ that my
> difficulty is not specific to Kterm, but would appear under Xterm
> as well.
> 
> Our mail server (nomolog) is a Sun SS5 running Redhat Linux 4.1.
> My own machine runs TurboLinux-J 2.0.  I do most of the system
> work on the mail server via Kterm, which I have configured to run
> from a *Wharf button in my ~/.steprc file thus:
> 
>   *Wharf Nomo     xterm-nomo.xpm Exec "-" rsh nomolog.nagoya-u.ac.jp /usr/bin/X11/kterm -ls -T 'Nomo'  -display 133.6.33.14:0 &

I think this should be:

*Wharf Nomo xterm-nomo.xpm Exec "kterm" kterm -T "Nomo" -e rsh nomolog.nagoya-u.ac.jp -display 133.6.33.14:0 &

> 
> This works swimmingly, except that the "@" key appears to trigger
> a "kill", and neither that key nor ^C works to kill running
> processes.  This is a real pain.  Among other things, it bars me
> from using the "mail" command, because I can't enter the "@" in
> an offsite address.
> 

try the above suggestion, it might fix it...

> I have tried starting the terminal with an without the -ls (login
> shell) option.  I have tried setting the TERMCAP environment
> variable to the same value it has on my TurboLinux system.  TERM
> is correctly set to "kterm" on the remote system, when invoked as
> a login shell.
> 

does the Sun know about 'kterm' in its termcap/terminfo database?
I'd suggest not using -ls with a remote shell.. the '-ls' in your original
command line is basically telling kterm to start as a login shell and then
rsh, which doesn't seem useful to me unless you need to reset your login
variables locally before rshing...?

> Stty reports the following on the remote (misbehaving) kterm:
> 
>   bash$ stty
>   speed 9600 baud; line = 0;
>   intr = ^?; erase = #; kill = @; start = <undef>; stop = <undef>;
>   susp = <undef>; dsusp = <undef>; rprnt = M-^?; werase = M-^?; lnext = M-^?;
>   flush = M-^?;
>   -brkint -imaxbel
>   -iexten -echoctl -echoke
>   bash$ 
> 
> It reports this status regardless of the value of TERM, and
> regardless of whether TERMCAP is set or not.  Issuing the
> following does NOT restore "@" as a useful key --- I still get a
> bell when it is pressed:
> 
>   stty kill undef
> 
> The only way I appear to be able to get a normal terminal is by
> opening a Kterm on the local machine and telnetting through to
> the server.  I can write a little Expect script to make this
> transparent, but it bugs me when things don't work as (I think)
> they ought, and sooner or later this will come around and bite me
> again anyway.
> 
> Cheers,
> -- 
> -x80
> Frank G Bennett, Jr         @@
> Faculty of Law, Nagoya Univ () email: bennett@example.com
> Tel: +81[(0)52]789-2239     () WWW:   http://rumple.soas.ac.uk/~bennett/
> ---------------------------------------------------------------
> Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691
> Next Meeting: 12 December, 12:30 Tokyo Station Yaesu central gate
> ---------------------------------------------------------------
> Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
> 

--------------------------------------------------
Scott M. Stone <sstone@example.com, sstone@example.com>
               <sstone@example.com>
Head of TurboLinux Development/Systems Administrator
Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)
http://www.pht.com		http://armadillo.pht.co.jp
http://www.pht.co.jp	        http://www.turbolinux.com


---------------------------------------------------------------
Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Meeting: 12 December, 12:30 Tokyo Station Yaesu central gate
---------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp