rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Boyd Roberts <boyd@prl.dec.com>
To: rc@archone.tamu.edu
Subject: Re: early reaction(s) to rc
Date: Fri, 23 Aug 1991 12:07:40 -0500	[thread overview]
Message-ID: <9108231907.14113.rc.bafiy@prl.dec.com> (raw)
In-Reply-To: <9108231651.AA27879@margay.cs.wisc.edu>

    I have suggested to Byron making the rc flags available in a special
    variable.  I think the Plan 9 rc does this, but I don't have my docs
    handy to check.

I've been thinking about `rcmain' for a while here Byron.  It gets executed
on every rc invocation.  It cleans up a lot of bad gore to do with
interactiveness, because the command line option processing is done in
this global rc script.  I spoke to Duff about it, I know you think it's
hideous, but it's a lot cleaner than special:

  - signals
  - variables
  - braindamage

You don't want `set' in rc.  You have arrays already, and with the trivial
number of options available, there's no point in going `set -x' or whatever.

For gods sake lets keep the shell stable, and concentrate on getting
the bugs out and _not_ the options in!

Duff told me:

    rcmain does the flags that affect initialization, to wit:
          -p      `protected' -- don't read functions, set path=(. /bin)
          -c      execute a command given on the command line
          -i      `interactive' -- print prompts for commands
          -l      `login shell' -- read $home/lib/profile before user's commands

I think it's a really neat idea.  We should do it.  It also solves a headache
I have here with DEC X invoking rc with this braindamaged `-s' option when i
log in -- gag.


  reply	other threads:[~1991-08-23 17:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1991-08-23 16:51 DaviD W. Sanderson
1991-08-23 17:07 ` Boyd Roberts [this message]
  -- strict thread matches above, loose matches on Subject: below --
1991-08-27  6:24 Paul Haahr
1991-08-27  7:15 ` Chris Siebenmann
1991-08-27 10:22 ` Boyd Roberts
1991-08-23 20:47 Arnold D. Robbins
1991-08-24  0:15 ` John Mackin
1991-08-24  3:48   ` John Mackin
1991-08-23 16:24 Arnold D. Robbins
1991-08-27  2:33 ` Chris Siebenmann
1991-08-23  1:36 new list subscriber Byron Rakitzis
1991-08-23 13:40 ` early reaction(s) to rc John Mackin
1991-08-27  2:28   ` Chris Siebenmann

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=9108231907.14113.rc.bafiy@prl.dec.com \
    --to=boyd@prl.dec.com \
    --cc=rc@archone.tamu.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).