From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from burdell.cc.gatech.edu ([130.207.3.207]) by hawkwind.utcs.utoronto.ca with SMTP id <24132>; Wed, 30 Nov 1994 10:59:15 -0500 Received: from penfold.cc.gatech.edu (arnold@penfold.cc.gatech.edu [130.207.3.249]) by burdell.cc.gatech.edu (8.6.9/8.6.9) with ESMTP id KAA16848 for ; Wed, 30 Nov 1994 10:59:06 -0500 Received: (from arnold@localhost) by penfold.cc.gatech.edu (8.6.9/8.6.9) id KAA28311 for sam-fans@hawkwind.utcs.toronto.edu; Wed, 30 Nov 1994 10:59:05 -0500 From: arnold@cc.gatech.edu (Arnold Robbins) Message-Id: <199411301559.KAA28311@penfold.cc.gatech.edu> Date: Wed, 30 Nov 1994 10:59:04 -0500 In-Reply-To: Scott Schwartz's 28-line message on Nov 29, 8:22pm X-Ultrix: Just Say NO! X-Important-Saying: Premature Optimization Is The Root Of All Evil. X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: sam-fans@hawkwind.utcs.toronto.edu Subject: Re: 9menu >| == Rob > == Scott > | i disagree: the SHELL variable is conventionally just what you want: > | an indication of what interactive shell the user desires. the argument > | about make is spurious because make's functioning requires a > | standard shell; 9menu is for interactive applications, a different > | subject entirely. > > That's the crucial point: is 9menu itself an interactive application, > or is it a tool that that should support a standard syntax? My > impression is that the latter is the more useful view, because it > permits users to exchange 9menu command lines without depending upon > which interactive shell each of them uses. I have to admit that this is mostly how I envision 9menu, as a tool, not an interactive application. (It's interactive through the mouse, but that's orthogonal to the issue here.) My own expectation is that 9menu commands would run shell scripts that execute the larger tasks, and those scripts can be in any shell you like, via !#. This has the major advantage that you can edit the shell script without having to restart 9menu each time. I haven't completely decided yet how to deal with this. I'm semi-leaning towards a command line option -shell, instead of $SHELL. Arnold