From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from galapagos.cse.psu.edu ([130.203.2.12]) by hawkwind.utcs.utoronto.ca with SMTP id <24126>; Tue, 29 Nov 1994 20:22:57 -0500
Received: from localhost by galapagos.cse.psu.edu with SMTP id <12686>; Tue, 29 Nov 1994 20:22:36 -0500
To:	rob@plan9.research.att.com
cc:	sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: 9menu 
In-reply-to: Your message of "Tue, 29 Nov 1994 12:10:14 EST."
             <94Nov29.122228est.24126@hawkwind.utcs.utoronto.ca> 
Date:	Tue, 29 Nov 1994 20:22:23 -0500
From:	Scott Schwartz <schwartz@galapagos.cse.psu.edu>
Message-Id: <94Nov29.202236est.12686@galapagos.cse.psu.edu>


| 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.