From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from uucp-gw-1.pa.dec.com ([16.1.0.18]) by archone.tamu.edu with SMTP id <22533>; Tue, 27 Aug 1991 02:05:54 -0500
Received: by uucp-gw-1.pa.dec.com; id AA13020; Tue, 27 Aug 91 00:00:17 -0700
Received: by adobe.com (4.0/SMI-4.0)
	id AA21539; Mon, 26 Aug 91 23:24:10 PDT
Date: Tue, 27 Aug 1991 01:24:10 -0500
From: haahr@adobe.com (Paul Haahr)
Message-Id: <9108270624.AA21539@adobe.com>
To: cks@hawkwind.utcs.toronto.edu, rc@archone.tamu.edu
Subject: Re: early reaction(s) to rc

i used to set up a different history file for each window, and
just had xterm run an rc script which then invoked rc.  no muss,
no fuss, and didn't require any changes to rc.  Byron mentioned
last week that he uses one history file for all his windows; i
tried this last week, and now say i think it is the way to go.

as for per window startup commands themselves, if they are necessary
(the only thing my script did was set $history; everything else was
inherited) then just run a script that later invokes an interactive
rc.  one extra fork/exec is not that bad.  (or you can always do a
	. -i /dev/tty
if you really want to save that fork/exec)

on the other hand, it might (just MIGHT, i'm not advocating this)
be nice to be able to specify a different file that could be execute
prior to running rc, just like $home/.rcrc; maybe
	rc -L foo
would start an rc processes that did a . foo to start.