From: culliton@srg.af.mil (Tom Culliton x2278)
To: cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: Command execution
Date: Thu, 25 Jun 1992 17:56:35 -0400 [thread overview]
Message-ID: <9206251756.aa10707@ceres.srg.af.mil> (raw)
cks> if you invoke the absolute
cks> path name, you *mean* the absolute path name.
I can still imagine ways that it might be useful, but no big deal.
cks> 'x/y' vs. './x/y' has been hashed out before in the mailing list;
cks> check the archives. I belive Pike just considered it the right
cks> approach. I use it for the same sort of things that David Moore does;
cks> to keep infrequently-used stuff off my path.
I probably missed it, having only been on the mailing list since early
December. It could definitely be made clearer in the man page,
especially since it's rather different from most shells.
next reply other threads:[~1992-06-25 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-25 21:56 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-06-24 21:19 Tom Culliton x2278
1992-06-24 23:04 ` David Moore
1992-06-25 21:22 ` Chris Siebenmann
1992-06-24 19:10 Tom Culliton x2278
1992-06-24 20:19 ` 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=9206251756.aa10707@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=cks@hawkwind.utcs.toronto.edu \
--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).