sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: arnold@cc.gatech.edu (Arnold Robbins)
To: sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: 9menu
Date: Wed, 30 Nov 1994 10:59:04 -0500	[thread overview]
Message-ID: <199411301559.KAA28311@penfold.cc.gatech.edu> (raw)
In-Reply-To: Scott Schwartz's 28-line message on Nov 29,  8:22pm

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


             reply	other threads:[~1994-11-30 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-30 15:59 Arnold Robbins [this message]
  -- strict thread matches above, loose matches on Subject: below --
1994-11-29 17:10 9menu rob
1994-11-30  1:22 ` 9menu Scott Schwartz
1994-11-29 17:09 9menu Arnold Robbins
1994-11-29 15:32 9menu Arnold Robbins
1994-11-29 15:10 9menu Arnold Robbins
1994-11-29 16:10 ` 9menu Scott Schwartz
1994-11-29  3:08 9menu Scott Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199411301559.KAA28311@penfold.cc.gatech.edu \
    --to=arnold@cc.gatech.edu \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).