home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!phylo.genetics.washington.edu!zeno
- From: zeno@phylo.genetics.washington.edu (Sean Lamont)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: tcsh
- Date: 6 Jan 1993 21:05:06 GMT
- Organization: University of Washington, Seattle
- Lines: 21
- Message-ID: <1ifhi2INNcr7@shelley.u.washington.edu>
- References: <1993Jan6.155021.23331@ms.uky.edu>
- NNTP-Posting-Host: phylo.genetics.washington.edu
-
- In article <1993Jan6.155021.23331@ms.uky.edu> iguana@mik.uky.edu writes:
- >Cshell is generally accepted over Bourne shell (sh) for the fact that it
- >allows shell programming in the C language. TCshell is often used because
- >it allows for WATCHes to be set. For instance, I use TCshell because I can
- >leave a terminal window open and it will update me as to who is logging
- >into and off my machine.
- >
-
- What a totally bogus statement. Any reasonable shell programmer uses
- bourne shell just because it's more flexible. And cshell does NOT allow shell
- programming in the C language, just some of the syntax is shared.
-
- tcsh has a number of features that are desirable: Command-history scrollback,
- tab filename completion, watches, periodically executed commands,
- date/time/cwd in the prompt string, and many others.
-
- --
- Sean T. Lamont | "Don't oppress me, It's
- zeno@genetics.washington.edu | 'computer of color!' "
- lamont@abstractsoft.com |_______________________________
- Abstract Software
-