From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from albatross.prod.itd.earthlink.net ([207.217.120.120]) by hawkwind.utcs.toronto.edu with SMTP id <75642>; Tue, 26 Feb 2002 21:06:43 -0500 Received: from user-vcaunld.dsl.mindspring.com ([216.175.94.173] helo=rakitzis.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16fsKe-0004MD-00; Tue, 26 Feb 2002 16:52:32 -0800 Received: (from byron@localhost) by rakitzis.com (8.11.0/8.11.0) id g1R0qNS28877; Tue, 26 Feb 2002 16:52:23 -0800 Date: Tue, 26 Feb 2002 19:52:23 -0500 From: Byron Rakitzis Message-Id: <200202270052.g1R0qNS28877@rakitzis.com> To: rc@hawkwind.utcs.toronto.edu, tjg@star.le.ac.uk Subject: Re: non login "rc" needs customized environment Okay, here's a suggestion. What if by default a non-interactive rc executes .rcrc, but it does so implicitly with the -n flag set. Then, we need a builtin to be able to turn off -n, so that the non- interactive portions of .rcrc might be interpreted. Finally, there also then needs to be a mechanism for avoiding the infinite recursion of .rcrc's. An example .rcrc: # # Non-interactive stuff goes here # exec +n # made-up builtin path=(/a/bin /b/bin /c/bin) # # Interactive stuff goes here # exec -n # made-up builtin stty dec It's convoluted because I want rc to preserve compatability with the old .rcrc semantics: i.e., I want an old .rcrc to work properly even via rsh. Maybe this is a holy grail not worth pursuing since who likes the old semantics of rsh anyway? Byron.