Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Kterm/Xterm remote windows config
- To: tlug@example.com
- Subject: Re: tlug: Kterm/Xterm remote windows config
- From: Rex Walters <rex@example.com>
- Date: Tue, 13 Oct 1998 14:02:28 +0900
- Content-Transfer-Encoding: 8bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <Pine.LNX.3.96LJ1.1b7.981013125010.2090v-100000@example.com>; from Scott Stone on Tue, Oct 13, 1998 at 12:58:42PM +0900
- Mail-Followup-To: tlug@example.com
- References: <199810130344.MAA10157@example.com> <Pine.LNX.3.96LJ1.1b7.981013125010.2090v-100000@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
>>>>> "Scott" == Scott Stone writes: (on 13 Oct 98) Scott> > *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 & Scott> Scott> I think this should be: Scott> Scott> *Wharf Nomo xterm-nomo.xpm Exec "kterm" kterm -T "Nomo" -e rsh nomolog.nagoya-u.ac.jp -display 133.6.33.14:0 & Better, but not ideal. You've avoided having the xclient (kterm) speaking to the X-server over the network, but it's better to use fast IPC. Remove the "-display 133.6.33.14:0" -- your startup scripts for X should (!) give you the best value for $DISPLAY (usually ":0.0") to avoid unnecessary overhead. >>>>> Frank Bennett writes: (on 13 Oct 98) Frank> Stty reports the following on the remote (misbehaving) kterm: Frank> Frank> bash$ stty Frank> speed 9600 baud; line = 0; Frank> intr = ^?; erase = #; kill = @; start = <undef>; stop = <undef>; Frank> susp = <undef>; dsusp = <undef>; rprnt = M-^?; werase = M-^?; lnext Well this explains why ^C and @ don't do what you expect. You are expecting the interrupt function (intr) and a literal @ respectively. Your current settings have ^? (del) as the intr character, and @ as the line kill character (delete to beginning of line). The direct solution is simply: bash$ stty kill # typed "stty kill ctrl-V ctrl-U" bash$ stty intr # typed "stty kill ctrl-V ctrl-C" # (the ctrl-V unnecessary here, # but it's nice to know how to # quote) But what you probably are looking for is: bash$ export TERM=kterm # or TERM=xterm if kterm isn't # in terminfo/termcap bash$ eval `tset -s $TERM` Erase is delete. Kill is control-U (^U). Interrupt is control-C (^C). bash$ stty -a speed 9600 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; Most likely your remote system doesn't know anything about kterms. Regards, -- Rex --------------------------------------------------------------- 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
- Follow-Ups:
- Re: tlug: Kterm/Xterm remote windows config
- From: "Stephen J. Turnbull" <turnbull@example.com>
- Re: tlug: Kterm/Xterm remote windows config
- From: Scott Stone <sstone@example.com>
- References:
- tlug: Kterm/Xterm remote windows config
- From: Frank Bennett <bennett@example.com>
- Re: tlug: Kterm/Xterm remote windows config
- From: Scott Stone <sstone@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: beeps from motherboards again
- Next by Date: Re: tlug: beeps from motherboards again
- Prev by thread: Re: tlug: Kterm/Xterm remote windows config
- Next by thread: Re: tlug: Kterm/Xterm remote windows config
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links