Newest at the top
| 2025-01-23 18:31:23 +0100 | <Guest12> | I was hoping there was a way to interact directly with the place where xmonad stores the current screen number, and just say now it's this (because it's easy to compute it from workspace name 0_2 => screen 0 so i need to switch to screen 1) but it seems its harder to do it :) |
| 2025-01-23 18:28:47 +0100 | <Guest12> | [*0_6*, 1_2, 2_2, 3_4]) but I think this will make the config very complicated to understand later... |
| 2025-01-23 18:28:47 +0100 | <Guest12> | I see, thanks guys for the info! I could actually hack into how M-1 M-2 keybindings work and like when "switching" (actually swapping) to different screens, I could use some kind of state to remember the current workspace on each virtual screen (like a list [0_3, 1_2, 2_2, 3_4] and if i'm on 0_6 and i go right I get on 1_2 and the list would become |
| 2025-01-23 18:21:04 +0100 | <geekosaur> | (tbh I'm amazed IndependentScreens works as well as it does) |
| 2025-01-23 18:20:42 +0100 | <geekosaur> | I think it would be possible to modify IndependentScreens to do this, but it would make an already complicated module even more complicated and failure-prone |
| 2025-01-23 18:19:39 +0100 | <geekosaur> | and you can't convert planes to IndependentScreens-style workspaces or vice versa, so switching from single to multiple monitor mode would require logging out of the session (not just restarting xmonad, that would preserve workspace marshaling) |
| 2025-01-23 18:18:37 +0100 | <geekosaur> | the problem there is a second screen will show another workspace from the current plane and can't be made to show something from a different plane |
| 2025-01-23 18:17:16 +0100 | <geekosaur> | that's more or less X.A.Plane, which I mentioned earlier |
| 2025-01-23 18:16:09 +0100 | <fizzie> | Is stopping using IndependentScreens-style workspaces and just using one combined set that can be shown on any screen an option? That plays well with a changing number of monitors (it just affects how many you can have visible at once). |
| 2025-01-23 18:15:24 +0100 | <geekosaur> | hm. no, and I don't think (a) you could make zaphod mode work here (b) xmonad core would need patching to support it (it always uses X11 Screen 0) |
| 2025-01-23 18:15:18 +0100 | <Guest12> | "(Making mouse motion make sense left as an exercise to the reader for this double-wide-with-panning scheme.)" this was actually what i wanted to achieve, to use a mouse gesture to switch from screen 0 to screen 1 to get more real estate ;) |
| 2025-01-23 18:13:32 +0100 | <Guest12> | Also would starting another xmonad instance on a different tty help? I think the downside is that I would lose the ability to comunicate between workspaces on different ttys |
| 2025-01-23 18:12:24 +0100 | <geekosaur> | that would have a propensity for moving you to the other monitor while leaving the viewport on the real one |
| 2025-01-23 18:12:01 +0100 | <fizzie> | Also you'd maybe lose your mouse cursor into the non-visible monitor all the time. ;) |
| 2025-01-23 18:10:46 +0100 | <fizzie> | I feel like even if you managed to make a "non-visible" monitor with XRandR with the right resolution, that still wouldn't easily let you swap which workspaces you're seeing on the real one. |
| 2025-01-23 18:09:27 +0100 | <Guest12> | the resolution was the problem because the xorg dummy was for servers where they dont need full hd ;( |
| 2025-01-23 18:09:15 +0100 | <fizzie> | As geekosaur said, other programs not understanding that it's supposed to behave as two separate monitors would probably be an issue. |
| 2025-01-23 18:09:08 +0100 | <geekosaur> | xmobar won't know about layoutScreens |
| 2025-01-23 18:08:55 +0100 | <Guest12> | maybe using both panning and layoutscreens would work |
| 2025-01-23 18:08:21 +0100 | <Guest12> | I was thinking about the panning thing, but i still got xmobar displayed, so i think it will just get stretched |
| 2025-01-23 18:08:16 +0100 | <fizzie> | (Making mouse motion make sense left as an exercise to the reader for this double-wide-with-panning scheme.) |
| 2025-01-23 18:08:07 +0100 | <geekosaur> | you should be able to specify a resolution with --mode |
| 2025-01-23 18:07:40 +0100 | <Guest12> | Yes, it's like i want to make screen 0 black, and start up screen 1, I dont want to split my current screen. I looked into xrandr yesterday, and it said I should do a dummy screen and switch to it but I couldn't get it to work (also it had like 1280x1020 resolution) |
| 2025-01-23 18:07:39 +0100 | <fizzie> | Well, the panning *and* the XMonad focus. |
| 2025-01-23 18:06:59 +0100 | <fizzie> | Here's one real kludgy way I can think of that might be *possible* (but not a good idea): when there's just one connected monitor, use XRandR to configure a desktop that's twice the size of the monitor, with panning, and then use LayoutScreens to have XMonad split it into two logical screens; then make the M-w/M-e keybindings affect the panning rather than anything XMonad is doing. |
| 2025-01-23 18:04:52 +0100 | <fizzie> | I guess you didn't want to split the one remaining monitor but have it present one or the other, right. |
| 2025-01-23 18:04:49 +0100 | mc47 | (~yecinem@p200300ee0f038dc39287614d4759a7ca.dip0.t-ipconnect.de) (Ping timeout: 248 seconds) |
| 2025-01-23 18:03:10 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Ping timeout: 244 seconds) |
| 2025-01-23 18:02:26 +0100 | <geekosaur> | LayoutScreens splits the physical screen as xmonad sees it, that's not what is wanted here. Also other programs don't know about it so you get weird behavior |
| 2025-01-23 18:02:22 +0100 | <fizzie> | https://hackage.haskell.org/package/xmonad-contrib-0.18.1/docs/XMonad-Layout-LayoutScreens.html -- should allow you to have XMonad treat a single physical screen as multiple screens that would be treated the same way as if they were real ones. |
| 2025-01-23 18:01:57 +0100 | <geekosaur> | but I think trying to pull that off would be difficult |
| 2025-01-23 18:01:37 +0100 | <geekosaur> | only in the single screen case |
| 2025-01-23 18:01:30 +0100 | <geekosaur> | I don't think there's a good way to do what you want, or switch to using XMonad.Actions.Plane |
| 2025-01-23 18:01:12 +0100 | <fizzie> | Just going by "way to simulate multiple (virtual) screens on a single physical screen" rather than the rest, there's also XMonad.Layout.LayoutScreens. |
| 2025-01-23 18:01:11 +0100 | <geekosaur> | hm, no, that wouldn't work either, it would switch to the "other screen" but the viewport would still be on the real screen |
| 2025-01-23 18:00:40 +0100 | <geekosaur> | I think there's something you can do with xrandr to make it tell xmonad there are two screens; that's about the only way I can think of. But I think you'll have to talk to liskin if he's around; I don't seem to do well with xrandr for some reason |
| 2025-01-23 17:47:37 +0100 | <Guest12> | I think what I'm asking is if there is a way to simulate multiple (virtual) screens on a single physical screen. |
| 2025-01-23 17:44:49 +0100 | <Guest12> | with empty workspaces (not hacking my M-1, M-2, M-X etc keybinds that are doing: "windows $ onCurrentScreen W.view (workspaces' conf !! X)" Code: https://pastebin.com/LFaRxQ0A |
| 2025-01-23 17:44:49 +0100 | <Guest12> | would like to "swap" to screen 1, workspace 1_1 (basically extending my 9 workspaces). My code currently works using greedyView (I can swap to workspace 1_1), but that does not change the screen, it only swaps to that workspace... The screen is still 0, so M-5 would send me to 0_5 instead of 1_5. Is there a way to *switch* completely to screen 1 |
| 2025-01-23 17:44:48 +0100 | <Guest12> | Hello! I have a problem with xmonad. I am reusing my config when using one screen or multiple screens. When multiple screens are connected, I can swap to workspaces (on different screens) with M-w (to the left) and M-e (to the right). When using only one screen i would still want to be able to do this (like if I'm on workspace 0_2 and I press M-e i |
| 2025-01-23 17:34:46 +0100 | Guest12 | (~Guest12@2a02:2f0f:6109:3500:6bf:1bff:fec0:9354) |
| 2025-01-23 17:33:02 +0100 | m5zs7k | (aquares@web10.mydevil.net) m5zs7k |
| 2025-01-23 17:30:13 +0100 | m5zs7k | (aquares@web10.mydevil.net) (Ping timeout: 248 seconds) |
| 2025-01-23 17:06:32 +0100 | Digitteknohippie | Digit |
| 2025-01-23 16:18:00 +0100 | ft | (~ft@p3e9bcab6.dip0.t-ipconnect.de) ft |
| 2025-01-23 16:16:01 +0100 | ft | (~ft@p3e9bcab6.dip0.t-ipconnect.de) (Client Quit) |
| 2025-01-23 16:14:14 +0100 | ft | (~ft@p3e9bcab6.dip0.t-ipconnect.de) ft |
| 2025-01-23 16:05:45 +0100 | RMSBach | (~guygastin@137.184.131.156) RMSBach |
| 2025-01-23 16:05:45 +0100 | Leary | (~Leary@user/Leary/x-0910699) Leary |
| 2025-01-23 16:05:45 +0100 | jzargo | (~jzargo@user/jzargo) jzargo |