FVWM: DISPLAY variable changing after running fvwm

From: John Giles <jgiles_at_efs-us.com>
Date: Wed, 05 Jul 2000 11:45:40 -0500

Hey.
I have $DISPLAY exported to "computer_name:0.0" before I run fvwm.
When I bring up an xterm inside fvwm, my DISPLAY variable has changed
to just ":0.0", when it should be "computer_name:0.0"... Why does fvwm
strip off the name of the computer in this variable ???

I have two monitors and all local x-applications are displayed
correctly...
My problem is running remote x-applications... The display never makes
it back because $DISPLAY is set to ":0.0" and not fully qualified to
"computer_name:0.0".... you see... And I don't want to export $DISPLAY
every time I start a new xterm...

I tried using the fvwm command "SetEnv DISPLAY computer_name:0.0"
and that sets $DISPLAY to "computer_name:0.0", but then all the
applications
show on :0.0 and never :0.1... doh, and double doh...

Has anyone else encountered this... I would like it if fvwm didn't
manipulate
the DISPLAY variable, or if there was a way to tell it not to ???

jgiles
jgiles_at_efs-us.com

--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Jul 05 2000 - 12:42:43 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:50 BST