> > Perhaps a better question is this:  Is it reasonable for a window
manager to
> > set DISPLAY if it subverts the value it inherits from the session
manager?
> 
> Probably yes. There are several cases, $DISPLAY is initially set or not,
> -d is given or not. I think it is ok to set $DISPLAY to what X says after
> all given input (if any) is processed.
> 

I'm not so sure.  If the session manager parents fvwm2 with a legitimate
$DISPLAY value already set (like :0.1), ignoring it and setting $DISPLAY
anyway seems risky, especially since Xlib _may_ tell fvwm2 that display is
"unix:0.1".  It seems to me _any_ window manager should attempt to use the
display handed to it if possible (either inherited through $DISPLAY or
hardwired via command line option), to keep the wm in sync with the session
manager's other children.

> 
> Just for a curious, what is your setup?
> 
> Real session manager and multi-screen display?
> 
> How do you restart, using which command on which screen?
> 

I am running a two-headed display under Solaris 7's dtsession (not
Xinerama).  At login, twin instances of the default window manager are
started.  I bring up an xterm on the right screen (:0.1) and kill the
right-side wm instance.  In that same window, I start fvwm2 manually:

  % /<path>/fvwm2 -s -f /<path>/<config_file>

I am able to recreate the problem with this minimalist <config_file>:

  ModulePath /<path>/modules:+
  AddToFunc StartFunction
  + I Echo $[DISPLAY]
  + I FvwmTaskBar
  + I FvwmCommandS

On startup, I always see in the xterm:

  [FVWM.1][Echo]:  :0.1

I restart using fvwm2's built-in root menu on the right screen.  Sometimes
on the first restart, I see the "wrong" answer:

  [FVWM.1][Echo]:  unix:0.1

Sometimes a few dozen restarts are required before I see it.  With my
"regular" (bigger) config file, only one or two restarts are required before
the problem occurs.

Gregg Dameron
--
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 [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to