rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: "David J. Fiander" <davidf@golem.waterloo.on.ca>
To: Byron Rakitzis <byron@netapp.com>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc 1.5
Date: Sat, 17 Apr 1993 07:51:55 -0400	[thread overview]
Message-ID: <9304170751.aa04405@golem.waterloo.on.ca> (raw)
In-Reply-To: Your message of "Fri, 16 Apr 93 18:21:39 EDT." <9304162221.AA25866@netapp.netapp.com>

>That's a good question. I'm hoping to freeze rc. I also don't feel
>the need to bring rc "into line" with anything else. So offhand I
>would say no. The flag command is present in plan9 rc for a very
>specific reason (/lib/rcmain).

It's also there so scripts can change flags.  I would like to
be able to write scripts that turn on the -x flag internally,
when their debug flag is specified on the command line.

>And I don't want dot to search
>my path. 

[deletion]

>and "." is at the end of my path? Does this mean I run /bin/test
>as rc input? (THIS IS WHAT /bin/sh ACTUALLY DOES!!)

Actually, /bin/sh, /bin/ksh, and the POSIX.2 shell all check
the current directory for a file named "test", and _then_
search the path for a file named "test" which is also
executable.

The reason I would like "." to search the path is that then I
can create the directory /usr/bin/rclib, and store
scripts in there.  Then my scripts can just say

	. rclib/read

to load the read function that I have stored there.

- David


  reply	other threads:[~1993-04-17 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-04-16 22:21 Byron Rakitzis
1993-04-17 11:51 ` David J. Fiander [this message]
1993-04-19 11:59   ` Chet Ramey
  -- strict thread matches above, loose matches on Subject: below --
1993-04-17 16:56 Paul Haahr
1993-04-17 16:47 Alan Watson
1993-04-16 19:14 Memory leaking Byron Rakitzis
1993-04-16 22:04 ` rc 1.5 David J. Fiander

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=9304170751.aa04405@golem.waterloo.on.ca \
    --to=davidf@golem.waterloo.on.ca \
    --cc=byron@netapp.com \
    --cc=rc@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).