From: byron@netapp.com (Byron Rakitzis)
To: davidf@golem.waterloo.on.ca
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc 1.5
Date: Fri, 16 Apr 1993 18:21:39 -0400 [thread overview]
Message-ID: <9304162221.AA25866@netapp.netapp.com> (raw)
>Will 1.5 be brought into line with the Plan 9 man page?
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). And I don't want dot to search
my path. What if I do:
; cat >test <<EOF
garbage
EOF
; . test
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!!)
No thank you.
next reply other threads:[~1993-04-16 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-16 22:21 Byron Rakitzis [this message]
1993-04-17 11:51 ` David J. Fiander
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=9304162221.AA25866@netapp.netapp.com \
--to=byron@netapp.com \
--cc=davidf@golem.waterloo.on.ca \
--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).