Path: utzoo!utgpu!news-server.csri.toronto.edu!utcs.toronto.edu!cks
Newsgroups: comp.unix.shell
From: cks@hawkwind.utcs.toronto.edu (Chris Siebenmann)
Subject: Re: separate the command language and interactive shell
Message-ID: <1991May14.015618.26661@jarvis.csri.toronto.edu>
Organization: Ziebmef home away from home
References: <2987@optima.cs.arizona.edu> <1991May10.184707.13965@sco.COM>
Date: 14 May 91 05:56:18 GMT
Lines: 18

john@sco.COM (John R. MacMillan) writes:
| Ideally, the ``dead weight'' completion code that is indeed common
| (scanning the directory and matching) never gets paged in when the
| program is running in batch mode.  And if you put it in a shared
| library, it doesn't even take up disk space.

 There are a surprising amount of use of completion/shell filename
expansion used in 'batch' shell scripts, at least in the shell scripts
I tend to write. Most of the nominally interactive features in my
(sh-like) shell tend to get used in shell scripts, and most of the
nominally shell-script oriented ones have gotten used for interactive
stuff.

--
	"This Vi mode "feels" like Vi to me; it drives me nuts in the
	 ways that I am used to Vi driving me nuts." 
		- Brian Fox
cks@hawkwind.utcs.toronto.edu	           ...!{utgpu,utzoo,watmath}!utgpu!cks