home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!auspex-gw!guy
- From: guy@Auspex.COM (Guy Harris)
- Newsgroups: comp.sys.sun.apps
- Subject: Re: openwin and DISPLAY
- Message-ID: <14478@auspex-gw.auspex.com>
- Date: 4 Sep 92 17:54:28 GMT
- References: <1992Sep3.121811.22606@cbnewsh.cb.att.com> <1992Sep3.181602.20133@lsil.com> <1992Sep4.113258.1884@cbnewsi.cb.att.com>
- Sender: news@auspex-gw.auspex.com
- Distribution: na
- Organization: Auspex Systems, Santa Clara
- Lines: 34
- Nntp-Posting-Host: bootme.auspex.com
-
- >but openwin is damaged -- it won't [easily] run anywhere but the
- >console. i tried setting DISPLAY to the machine:0 form, and ow just
- >barked and died (a clean death -- i don't think it suffered much).
-
- "Died" in what sense?
-
- When I did
-
- DISPLAY=unix:0 /usr/bin/X11/xterm
-
- on my machine running OW 2.0, the "xterm" came up just fine, and when I
- did
-
- DISPLAY=unix:0 shelltool
-
- the "shelltool" (yes, it's the XView one, not the SunView one) came up
- just fine.
-
- Thus, the suggestion of the poster to whom you're responding, namely:
-
- X uses the DISPLAY variable to indicate the host running the X server,
- "and the screen number (do a "man X" for details).
- "To redefine DISPLAY for this application, try running the program via env:
- " env DISPLAY=whatever your_application and its arguments
-
- i.e., set DISPLAY to a different value when running that *particular*
- application, should work just fine.
-
- Now, of course, given that ":0", not "unix:0", is, as far as I know, the
- official X11R4-and-later politically-correct,
- non-oppressively-UNIX-centric way of saying "display 0 on the machine on
- which the application is running", if the application in question is
- *itself* looking at DISPLAY, it should be taught about ":0". It may
- just have been linked, statically, with an older X11 library, though.
-