starting workspace for each screen
Hello again,
Does anyone know if there's any way to set the starting workspace for each monitor?
Maybe a way to fake some keystrokes would work as well if there's no easy way to
do this in xmonad. For example, what I want to do, following the default xmonad
config, would be the equivalent of:
alt+e (select second monitor)
alt+8 (pick workspace 8)
alt+w (select first monitor again)
I use workspaces 1-7 for real work, and 8 is just for mplayer, so I want to put the
8th workspace on the second monitor and give back the input focus to the first
monitor.
Regards.
--
Jesús Guerrero
On Fri, Jun 13, 2008 at 09:38:44AM +0200, Jesús Guerrero wrote:
Hello again,
Does anyone know if there's any way to set the starting workspace for each monitor?
Maybe a way to fake some keystrokes would work as well if there's no easy way to do this in xmonad. For example, what I want to do, following the default xmonad config, would be the equivalent of:
alt+e (select second monitor) alt+8 (pick workspace 8) alt+w (select first monitor again)
I use workspaces 1-7 for real work, and 8 is just for mplayer, so I want to put the 8th workspace on the second monitor and give back the input focus to the first monitor.
Regards. -- Jesús Guerrero
Try startupHook? Something like this should work (assuming the default workspace names): startupHook = windows (W.view "1" . W.view "8" . W.view "2") Cheers, Spencer Janssen
Hello,
On Fri, 13 Jun 2008 02:58:28 -0500
Spencer Janssen
Try startupHook? Something like this should work (assuming the default workspace names):
startupHook = windows (W.view "1" . W.view "8" . W.view "2")
I am probably doing something wrong, but I get no results at all. And I can't see
anything in that code that resembles what I want to do (though my knowledge is very
limited). I think that the keybindings sequence I posted on my other mail was clear
enough, so I guess that I am doing wrong. I include that line on my config this way:
myStartupHook = windows (W.view "1" . W.view "8" . W.view "2")
[...]
main = xmonad defaults
defaults = defaultConfig {
[...]
, startupHook = myStartupHook
}
But I still get the same behavior. When xmonad starts up, workspace 1 goes to
screen 1, and workspace 2 goes to monitor 2. I have no clue about what that line
actually does. It's hard to come by a decent document that explains something useful
about this little details. I have no idea where those W.view, W.shift, and similar
things come from. I think I have to dive a bit more in the xmonad docs and try to
absorb a bit more.
Thanks for pointing me to startupHook. :)
--
Jesús Guerrero
On Fri, Jun 13, 2008 at 10:34:16AM +0200, Jes?s Guerrero wrote:
I am probably doing something wrong, but I get no results at all. No, he flubbed.
myStartupHook = windows (W.view "1" . W.view "8" . W.view "2") The dots compose functions from right to left, so this reads 'press mod-2, mod-8, mod-1', which obviously does nothing. Find out the default keybinding for mod-{w,e,r}, and substitute that in for the first and last.
On Fri, Jun 13, 2008 at 09:55:03AM -0700, Devin Mullins wrote:
On Fri, Jun 13, 2008 at 10:34:16AM +0200, Jes?s Guerrero wrote:
myStartupHook = windows (W.view "1" . W.view "8" . W.view "2") The dots compose functions from right to left, so this reads 'press mod-2, mod-8, mod-1', which obviously does nothing. Find out the default keybinding for mod-{w,e,r}, and substitute that in for the first and last. Okay, I flubbed, too. Not sure why it isn't working.
(Err.. there's no "too" about it, to be fair.) On Fri, Jun 13, 2008 at 10:34:16AM +0200, Jes?s Guerrero wrote:
actually does. It's hard to come by a decent document that explains something useful about this little details. Well you're treading between configuration and Haskell programming, so one answer is to broaden your search.
I have no idea where those W.view, W.shift, and similar things come from. I think I have to dive a bit more in the xmonad docs and try to absorb a bit more. The W.* functions come from: import qualified XMonad.StackSet as W which is surely at the top of your config. You can then track down the documentation for that module from xmonad.org.
participants (3)
-
Devin Mullins -
Jesús Guerrero -
Spencer Janssen