From: Chris Siebenmann <cks>
To: rc
Subject: Re: Command execution
Date: Thu, 25 Jun 1992 17:22:40 -0400 [thread overview]
Message-ID: <92Jun25.172253edt.2690@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: culliton's message of Wed, 24 Jun 92 17:19:34 -0400. <9206241719.aa07461@ceres.srg.af.mil>
[trapping regular absolute program names with function names:]
| This was exactly what I wanted to do. One of my friends likes to run a
| couple of obnoxious programs on my workstation when he drops by to
| visit and I'm not in the office.
This sounds like a social problem, not a software problem; if it's
really that bad, patch your own version of rc a bit. I wouldn't want
to twist the main rc version to do this; if you invoke the absolute
path name, you *mean* the absolute path name.
'x/y' vs. './x/y' has been hashed out before in the mailing list;
check the archives. I belive Pike just considered it the right
approach. I use it for the same sort of things that David Moore does;
to keep infrequently-used stuff off my path.
- cks
next prev parent reply other threads:[~1992-06-25 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-24 21:19 Tom Culliton x2278
1992-06-24 23:04 ` David Moore
1992-06-25 21:22 ` Chris Siebenmann [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-06-25 21:56 Tom Culliton x2278
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=92Jun25.172253edt.2690@hawkwind.utcs.toronto.edu \
--to=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).