Xinerama screen numbering seems to have changed

It seems that they're numbered from 1 rather than 0, so everything works OK if I do hunk ./Config.hs 175 - | (key, sc) <- zip [xK_w, xK_e, xK_r] [0..] + | (key, sc) <- zip [xK_w, xK_e, xK_r] [1..] and make the appropriate change to dmenuXinerama. Is that a deliberate change? (I'm indifferent to it; I'm just slightly concerned I might have broken something in my local build.)

On Sat, 07 Jul 2007 23:01:21 +0100
Bruce Stephens
It seems that they're numbered from 1 rather than 0, so everything works OK if I do
hunk ./Config.hs 175 - | (key, sc) <- zip [xK_w, xK_e, xK_r] [0..] + | (key, sc) <- zip [xK_w, xK_e, xK_r] [1..]
and make the appropriate change to dmenuXinerama. Is that a deliberate change? (I'm indifferent to it; I'm just slightly concerned I might have broken something in my local build.)
We number them from 0 in xmonad intentionally -- I'm not sure how the Xinerama patched dmenu numbers them. Jason wrote that patch, let's see what he has to say about this. Also, there was a bug in 'rescreen' that may be related to this. Do you use xrandr with multiple screens? Cheers, Spencer Janssen

On Sat, Jul 07, 2007 at 05:58:55PM -0500, Spencer Janssen wrote:
On Sat, 07 Jul 2007 23:01:21 +0100 Bruce Stephens
wrote: It seems that they're numbered from 1 rather than 0, so everything works OK if I do
hunk ./Config.hs 175 - | (key, sc) <- zip [xK_w, xK_e, xK_r] [0..] + | (key, sc) <- zip [xK_w, xK_e, xK_r] [1..]
and make the appropriate change to dmenuXinerama. Is that a deliberate change? (I'm indifferent to it; I'm just slightly concerned I might have broken something in my local build.)
We number them from 0 in xmonad intentionally -- I'm not sure how the Xinerama patched dmenu numbers them. Jason wrote that patch, let's see what he has to say about this.
Xinerama-patched dmenu uses 1-indexed screen numbers, whereas, as Spencer notes, xmonad users 0-indexed screen numbers. IIRC, it's been that way for at least a couple weeks, so I'm puzzled as to why you'd be running into breakage. Jason Creighton

Jason Creighton
Xinerama-patched dmenu uses 1-indexed screen numbers, whereas, as Spencer notes, xmonad users 0-indexed screen numbers.
Right, that's what I understood.
IIRC, it's been that way for at least a couple weeks, so I'm puzzled as to why you'd be running into breakage.
On rebooting, it seems to be back to what it ought to be. So I guess it was some kind of temporary glitch, though I can't imagine what. It did happen, though, honest: dmenu appeared on the second screen (or not at all), mod1-w did nothing, but mod1-e and mod1-r selected the two screens, etc. Weird, but quite probably nothing to do with xmonad.
participants (3)
-
Bruce Stephens
-
Jason Creighton
-
Spencer Janssen