From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: exec'ing with relative pathname
Date: Fri, 27 Sep 1991 22:27:58 -0500 [thread overview]
Message-ID: <91Sep27.232802edt.2719@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: chupchup's message of Fri, 27 Sep 91 22:12:07 -0400. <9109280312.AA09895@piggy.ucsb.edu>
This behavior matches the Plan 9 rc, and at least Rob Pike considered
it the right thing to do (when overheard at Usenix). It can be debated,
but given that Plan 9 rc does it that way I think we should as well.
It does have a certain charm and occasional elegance. For example,
we have a /local/bin/urep directory for UREP commands, but I don't
have it on my path; this way I can type 'urep/cmd' and it'll wind up
executing the right thing.
- cks
next prev parent reply other threads:[~1991-09-28 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-09-28 2:12 Robert Earl
1991-09-28 3:27 ` Chris Siebenmann [this message]
1991-09-30 15:54 Donn Cave
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=91Sep27.232802edt.2719@hawkwind.utcs.toronto.edu \
--to=cks@hawkwind.utcs.toronto.edu \
--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).