Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!watsup!mberkley From: mberkley@watsup.UUCP Newsgroups: comp.windows.x,comp.emacs Subject: Re: [liberte@b.cs.uiuc.edu: Re: -nw inconvenient for non X users] Message-ID: <14495@watmath.waterloo.edu> Date: Sun, 30-Aug-87 00:04:00 EDT Article-I.D.: watmath.14495 Posted: Sun Aug 30 00:04:00 1987 Date-Received: Sun, 30-Aug-87 10:29:50 EDT References: <8708251815.AA25757@dagda.think.com> Sender: daemon@watmath.waterloo.edu Reply-To: mberkley@watsup.waterloo.edu (Mike Berkley) Followup-To: comp.emacs Distribution: world Organization: U. of Waterloo, Ontario Lines: 26 Xref: utgpu comp.windows.x:915 comp.emacs:1613 In article <8708251815.AA25757@dagda.think.com> rlk@THINK.COM (Robert L. Krawitz) writes: >[Context of discussion: Dan was confused because he thought emacs >always tried to come up under X when it was compiled with X. Turned >out that he set his DISPLAY variable in his .login or the like]. Not everybody who uses X uses it for xterm. In the PAMI lab here at UW, we have 3 X-type display devices and a bunch of vt220's. The X displays are used mostly for displaying digital images, for displaying graphical descriptions of pattern analyses and for previewing documents. Most people do their work on a vt220 and then display their images on one of the three X displays - there just aren't enough X displays to go around. That means, that it is normal to have the DISPLAY env variable set, even though xterm is not being used. Emacs should cue on the TERM being xterm, rather than the DISPLAY variable being set. If I'm really using xterm, then it's guaranteed that my TERM variable will be xterm, then check the DISPLAY variable for which display to use. Mike Berkley, University of Waterloo ************************************************************************ *UUCP: {allegra,ihnp4,utcsri,utzoo}!watmath!watsup!mberkley * *Bitnet: mberkley@watdcs.BITNET * ************************************************************************