It won't, no. The exec causes the shell to vanish (so the second xmonad isn't seen at all). Try something like /home/eric/bin/xmonad & setenv DISPLAY=beryllium:0.1 exec /home/eric/bin/xmonad Presuming that works OK, you might want to start both insta

My script is currently the following (I use tcsh). /home/eric/bin/xmonad & setenv DISPLAY beryllium:0.1 exec /home/eric/bin/xmonad & wait However, the second screen still isn't loading correctly. Does everything look okay for this? Eric Thomas -------------------------------- It won't, no. The exec causes the shell to vanish (so the second xmonad isn't seen at all). Try something like /home/eric/bin/xmonad & setenv DISPLAY=beryllium:0.1 exec /home/eric/bin/xmonad Presuming that works OK, you might want to start both instances in the background and use wait (to wait for both) at the end of the script. Or some variant like that---I'm not sure what would be most convenient for someone running two window managers.

Eric Thomas
My script is currently the following (I use tcsh).
/home/eric/bin/xmonad & setenv DISPLAY beryllium:0.1 exec /home/eric/bin/xmonad & wait
However, the second screen still isn't loading correctly. Does everything look okay for this?
Try removing the other exec as well. [...]

Bruce Stephens
Eric Thomas
writes: My script is currently the following (I use tcsh).
/home/eric/bin/xmonad & setenv DISPLAY beryllium:0.1 exec /home/eric/bin/xmonad & wait
However, the second screen still isn't loading correctly. Does everything look okay for this?
Try removing the other exec as well.
Or (more primitively) just run one xmonad and see if you can run the other one from a terminal.
participants (2)
-
Bruce Stephens
-
Eric Thomas