From: arnold@cc.gatech.edu (Arnold Robbins)
To: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
Cc: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Subject: Re: 9menu
Date: Tue, 29 Nov 1994 12:09:07 -0500 [thread overview]
Message-ID: <199411291709.MAA27471@penfold.cc.gatech.edu> (raw)
In-Reply-To: Scott Schwartz's 22-line message on Nov 29, 11:10am
> | That's not unreasonable, what I should probably do is fix 9menu to
> | just use ${SHELL:-/bin/sh}.
>
> I don't know... Isn't it better to have a definate syntax that 9menu
> will use, rather than have it depend on some environment variable?
> (Think about makefiles that need SHELL=/bin/sh at the top to get around
> some versions of make doing this.) If anything, a command line option
> is better than importing SHELL, I think.
I agree, a command line option is better. Again, patches welcome, if not
I'll try to tackle it over the next week or so.
Arnold
next reply other threads:[~1994-11-29 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-11-29 17:09 Arnold Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-11-30 15:59 9menu Arnold Robbins
1994-11-29 17:10 9menu rob
1994-11-30 1:22 ` 9menu Scott Schwartz
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=199411291709.MAA27471@penfold.cc.gatech.edu \
--to=arnold@cc.gatech.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
--cc=schwartz@galapagos.cse.psu.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).