home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!ames!network.ucsd.edu!sdcc12!xm9
- From: xm9@sdcc12.ucsd.edu (richard g. adair)
- Newsgroups: comp.sys.hp
- Subject: Re: Exiting KSH with ^D
- Summary: hpterm vs xterm
- Keywords: shell, ksh, kornshell, HP-UX
- Message-ID: <42416@sdcc12.ucsd.edu>
- Date: 11 Dec 92 18:27:56 GMT
- References: <50235@shamash.cdc.com> <1992Dec8.143148.13973@rtsg.mot.com> <1992Dec10.020807.8189@cbfsb.cb.att.com>
- Sender: news@sdcc12.ucsd.edu
- Organization: Arete Associates, San Diego
- Lines: 15
- Nntp-Posting-Host: sdcc12.ucsd.edu
-
- In article <1992Dec10.020807.8189@cbfsb.cb.att.com> jpittas@cbnewsf.cb.att.com (john.pittas) writes:
- >Many people have answered the original question by saying the
- >solution is to set 'viraw' in ksh to allow immediate exit via
- >control-d. However, on other vendor's machines around here
- >(various Suns, 3B2s and Pyramids) I can exit ksh via ^D WITHOUT
- >having viraw set! So, there's something peculiar about HP's
- >ksh that's causing this behavior. Anyone have any insight on this?
-
- Are you using hpterm? I've noticed that hpterm requires a CR after
- the ^D, while xterm doesn't. Could this be a setable hpterm
- resource in the .Xdefault file?
-
- Tony Burzio
- Arete Associates
- San Diego, CA
-