home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!rpi!crdgw1!rdsunx.crd.ge.com!rdsunx!barnett
- From: barnett@grymoire.crd.ge.com (Bruce Barnett)
- Newsgroups: comp.sys.sun.misc
- Subject: Re: Problem running tsch in a cmdtool
- Message-ID: <BARNETT.92Nov13114724@grymoire.crd.ge.com>
- Date: 13 Nov 92 16:47:24 GMT
- References: <BARNETT.92Nov12113149@grymoire.crd.ge.com>
- <1du53vINN1u0@morrow.stanford.edu>
- Sender: usenet@crd.ge.com (Required for NNTP)
- Reply-To: barnett@crdgw1.ge.com
- Organization: GE Corp. R & D, Schenectady, NY
- Lines: 15
- In-Reply-To: pln@egret0.Stanford.EDU's message of 12 Nov 1992 17:43:27 GMT
- Nntp-Posting-Host: grymoire.crd.ge.com
-
- In article <1du53vINN1u0@morrow.stanford.edu> pln@egret0.Stanford.EDU (Patrick L. Nolan) writes:
-
- > : 4 run script
- > : 5 rlogin `hostname`
- >
- > Neither of these helps. Whenever I use ^P to back up the command
- > history, the command line gets corrupted after about 3 or 4 times,
- > the same as for "naked" tcsh. I've seen these things suggested
- > many times. Doesn't anybody actually test these ideas?
-
-
- It's true that I didn't test these. I have heard that it solves the
- problems for bash and ksh users. Perhaps it's a bug in tcsh, and not cmdtool?
- --
- Bruce Barnett <barnett@crd.ge.com> uunet!crdgw1!barnett
-