home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!morrow.stanford.edu!pln
- From: pln@egret0.Stanford.EDU (Patrick L. Nolan)
- Newsgroups: comp.sys.sun.misc
- Subject: Re: Problem running tsch in a cmdtool
- Date: 12 Nov 1992 17:43:27 GMT
- Organization: Stanford University
- Lines: 24
- Message-ID: <1du53vINN1u0@morrow.stanford.edu>
- References: <BARNETT.92Nov12113149@grymoire.crd.ge.com>
- Reply-To: pln@egret0.Stanford.EDU
- NNTP-Posting-Host: egret1.stanford.edu
- X-Newsreader: TIN [version 1.1 PL6]
-
- Bruce Barnett (barnett@grymoire.crd.ge.com) wrote:
- : In article <1992Nov12.075932.4600@ericsson.se> etxmesa@eos.ericsson.se (Michael Salmon) writes:
- : > 1 Don't use suntools
- : > 2 Use shelltool instead of cmdtool.
- : > 3 Unset edit in tcsh.
-
- This disables the most desireable feature of tcsh, as far as I'm
- concerned.
-
- : 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?
-
- : 6 use mouse-based textedit/style editing cmdtool already provides
-
- --
- * Patrick L. Nolan (415)723-0133 *
- * W. W. Hansen Experimental Physics Laboratory (HEPL) *
- * Stanford University *
- * Bitnet: PLN@SLACVM Internet: pln@egret0.stanford.edu *
-