Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.windows.x
Subject: Re: compatible .twmrc
Message-ID: <34661@news.Think.COM>
Date: 14 Mar 90 08:11:58 GMT
References: <9003131600.AA02569@lance>
Sender: news@Think.COM
Reply-To: barmar@think.com (Barry Margolin)
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 15

I've gotten several responses to my question about writing a .twmrc that
can be used in both R3 and R4.  The concensus is to have separate .twmrc's,
and make use of R4 twm's -f option, which allows specification of the
pathname of the .twmrc.  Another suggestion was to name the R4 .twmrc to
.twmrc.0, since R4 twm looks for .twmrc.<display#> first.  I was hoping for
a solution that didn't require maintenance of parallel files, but I guess
there isn't one.

Now my other question: why?  Why was twm changed incompatibly in this
manner?
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar