From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: RCRC
Date: Sat, 4 Sep 1993 19:05:57 -0400 [thread overview]
Message-ID: <9309042305.AA14291@oldp.astro.wisc.edu> (raw)
I don't propose to treat them the same within .rcrc. The rc that I
eventually exec from rsh sources my .rcrc at the moment, so I have the
following in my .rcrc:
[set path, define fns, etc.]
if ( test -t 0 ) {
[set tty, check mail, etc.]
}
There are many variations on this. Yes, you will have to rewrite your
.rcrc, but I was assuming that most people were already using wrappers
around rsh or rc to source .rcrc. Perhaps I was wrong.
next reply other threads:[~1993-09-04 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-04 23:05 Alan Watson [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-09-04 22:10 RCRC Alan Watson
1993-09-04 22:20 ` RCRC Chris Siebenmann
1993-09-05 12:00 ` RCRC John Mackin
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=9309042305.AA14291@oldp.astro.wisc.edu \
--to=alan@oldp.astro.wisc.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).