From: Byron Rakitzis <byron@archone.tamu.edu>
To: rc@archone.tamu.edu
Subject: say what you mean
Date: Mon, 30 Sep 1991 11:06:10 -0500 [thread overview]
Message-ID: <91Sep30.110621cdt.19044@archone.tamu.edu> (raw)
If you want to exec ./foo/bar, then why don't you type
./foo/bar
I don't see why
foo/bar
should automatically default to ./foo/bar even if you don't have . in
your path. Presumably . is not in your path for security purposes. If
so, it seems even more reasonable to not override $path in this way.
I'm sorry to get so defensive, but rc is not sh. The rule is very
simple and imho more intuitive than sh's. If the pathname is
"absolute", i.e., beginning with /, ./, or ../, then no path searching
is done. What is so complicated about that?
next reply other threads:[~1991-10-01 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-09-30 16:06 Byron Rakitzis [this message]
1991-10-01 14:36 ` interactive cd Paul D. Swasey
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=91Sep30.110621cdt.19044@archone.tamu.edu \
--to=byron@archone.tamu.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).