Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!think!mit-eddie!bacchus!rlk
From: rlk@athena.mit.edu (Robert L. Krawitz)
Newsgroups: comp.emacs
Subject: Re: X and gnu emacs problem
Message-ID: <349@bacchus.MIT.EDU>
Date: Thu, 19-Mar-87 23:19:46 EST
Article-I.D.: bacchus.349
Posted: Thu Mar 19 23:19:46 1987
Date-Received: Sat, 21-Mar-87 08:15:21 EST
Sender: daemon@bacchus.MIT.EDU
Reply-To: rlk@athena.MIT.EDU
Organization: MIT Project Athena
Lines: 25

In article <foo@bar.UUCP> various people write:
]
]Why start it from an offscreen  xterm at  all?   The significant information
]that'll  pass  down  to  gnuemacs is  the value  of $TERM....   So On my
]HP9000/300 (HPUX), I call a script (xgnu) from my .uwmrc menu entry that
]does the trick:
]
]#!/bin/sh
]# set TERM so that subprograms (like mh's scan) don't assume I'm using a 9836
]TERM=xterms
]export TERM
]exec gnuemacs -i -fg Green -bg Sienna -bd Black -cr White $*
]
]-- Niels.

Version 17 emacs did indeed look at the TERM variable to decide
whether or not to start up under X.  This behavior having been
declared bogus, Version 18 relies on the DISPLAY variable.

Later local versions of 17 (i. e. at Athena) had various intermediate
stages of workingness (e. g. -d would force use of X) but I don't
think any of these hacks ever made it out to the world.  V18 does do
the right thing however.

Robert^Z