From: Chris Siebenmann <cks>
To: rc
Subject: why I though 'rc -lc 'command'' didn't source .rcrc
Date: Wed, 28 Oct 1992 05:43:57 -0500 [thread overview]
Message-ID: <92Oct28.054400est.2771@hawkwind.utcs.toronto.edu> (raw)
I was testing rc in a 'clean' environment in order to get
consistent timings, via 'env - <things> time ...'. When I
tested Duff's rc, I listed an explicit value for $HOME, since
I was using startup files that would work with it. When I
tested Byron's rc, I forgot to specify a 'HOME=...' entry
(under the mental fog of thinking this would use the one in
my environment); of course, rc had no $HOME, had no idea of
where to look for .rcrc, and so couldn't run it.
I'm not certain if it's worth printing out an error message
if things don't seem to make sense, and in any case this is
not (by any means!) a common occurrence. Might be something
to think about, though.
- cks
reply other threads:[~1992-10-28 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=92Oct28.054400est.2771@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).