rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Byron Rakitzis <byron@rakitzis.com>
To: byron@rakitzis.com, schwartz@bio.cse.psu.edu
Cc: pk@TechFak.Uni-Bielefeld.DE, rc@hawkwind.utcs.toronto.edu
Subject: Re: non login "rc" needs customized environment
Date: Thu, 14 Feb 2002 23:11:29 -0500	[thread overview]
Message-ID: <200202150411.g1F4BTn06392@rakitzis.com> (raw)

>Take a look at what zsh does.  There are lots of cases one might
>want to handle, once you start in with different config files:

Hey, my rc did away with the system-wide rcrc implied in Duff's
paper.

All I'm saying is that you don't necessarily want .rcrc to run via rsh --
there might be stuff in there that depends on an interactive shell. Hence
the suggestion that a different mechanism be used.

That being said, I like to use stricter rules for my personal .rcrc:
it is idempotent, so I can always issue ". .rcrc" and be sure there
won't be any nonsense in my environment.

Byron.


             reply	other threads:[~2002-02-15  4:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15  4:11 Byron Rakitzis [this message]
2002-02-15 14:04 ` Tim Goodwin
2002-02-27  1:46   ` callum.gibson
2002-02-27  2:16     ` Chris Siebenmann
2002-02-27 13:32       ` Carlo Strozzi
2002-02-27 13:29   ` Carlo Strozzi
2002-02-27 22:24     ` Matt H
2002-02-27  6:13 ` Derek Fawcus
  -- strict thread matches above, loose matches on Subject: below --
2002-02-27  6:29 Byron Rakitzis
2002-02-27  6:26 Russ Cox
2002-02-27  0:52 Byron Rakitzis
2002-02-14 17:44 Byron Rakitzis
2002-02-15  0:18 ` Dave Mason
2002-02-15  3:21 ` Scott Schwartz
2002-02-14 13:35 Smarasderagd
2002-02-15  0:37 ` Greg A. Woods
     [not found] <chet@nike.ins.cwru.edu>
2002-02-13 20:36 ` Chet Ramey
2002-02-14  2:16   ` Scott Schwartz
2002-02-14 23:35     ` Markus Friedl
2002-02-15  3:05       ` Scott Schwartz
2002-02-13 19:21 Peter Koch

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=200202150411.g1F4BTn06392@rakitzis.com \
    --to=byron@rakitzis.com \
    --cc=pk@TechFak.Uni-Bielefeld.DE \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=schwartz@bio.cse.psu.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).