From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from goose.prod.itd.earthlink.net ([207.217.120.18]) by hawkwind.utcs.toronto.edu with SMTP id <48116>; Thu, 14 Feb 2002 23:12:39 -0500 Received: from user-vcaun21.dsl.mindspring.com ([216.175.92.65] helo=rakitzis.com) by goose.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16bZig-0002jF-00; Thu, 14 Feb 2002 20:11:34 -0800 Received: (from byron@localhost) by rakitzis.com (8.11.0/8.11.0) id g1F4BTn06392; Thu, 14 Feb 2002 20:11:29 -0800 Date: Thu, 14 Feb 2002 23:11:29 -0500 From: Byron Rakitzis Message-Id: <200202150411.g1F4BTn06392@rakitzis.com> To: byron@rakitzis.com, schwartz@bio.cse.psu.edu Subject: Re: non login "rc" needs customized environment Cc: pk@TechFak.Uni-Bielefeld.DE, rc@hawkwind.utcs.toronto.edu >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.