Date: Mon, 1 Jul 1996 13:55:46 -0600 From: Sean Kelly <kelly@fsl.noaa.gov> To: branson@widomaker.com Cc: fadorn19@idt.liberty.com, questions@FreeBSD.ORG Subject: Re: fvwm and x-windows Message-ID: <199607011954.TAA13251@gatekeeper.fsl.noaa.gov> In-Reply-To: <199607011847.OAA16496@garion.hq.ferg.com> (message from Branson Matheson on Mon, 01 Jul 1996 14:47:16 -0400)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Branson" == Branson Matheson <branson@widomaker.com> writes:
Branson> csh > setenv DISPLAY {hostname}:0.0
Branson> sh > DISPLAY={hostname}:0.0 ; export DISPLAY
Branson> ( replace {hostname} with your display. )
Or not. If you're actually logged on {hostname}, then you *want* the
DISPLAY to be just
:0.0
and NOT {hostname}:0.0. A display of :0.0 means use the local X
server serving the first display, through a local Unix socket in
/tmp/.X11-unix/X0. This is the fastest way to access a display.
In second place is a DISPLAY of localhost:0.0, which uses the loopback
interface lo0. In last place is a DISPLAY of {hostname}:0.0, which
uses the network interface.
Homework question: what's a *fourth* way to access a display (on
those displays that are configured for it)?
Branson> You might make yourself an .xinitrc that sets the window
Branson> manager. somthing like:
Branson> #!/bin/csh
Branson> setenv DISPLAY `hostname`:0.0
Yes, definitely wrong. When xinit is run, the DISPLAY environment
varialbe should already be set ... and set *correctly*.
On FreeBSD, it isn't so bad. But on HP/UX, playing xkobo with display
set to "{hostname}:0.0" is like molasses in January. But with it set
to ":0.0" it just screams!
--
sean Kelly
NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov
Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607011954.TAA13251>