Newest at the top
| 2025-01-24 07:22:23 +0100 | ft | (~ft@p508db1ba.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-01-24 03:57:06 +0100 | ft | (~ft@p508db1ba.dip0.t-ipconnect.de) ft |
| 2025-01-24 03:55:14 +0100 | ft | (~ft@p3e9bcab6.dip0.t-ipconnect.de) (Ping timeout: 248 seconds) |
| 2025-01-24 03:13:29 +0100 | dweller | (~dweller@178.62.146.60) dwelli |
| 2025-01-24 03:13:14 +0100 | dweller | (~dweller@178.62.146.60) (Ping timeout: 252 seconds) |
| 2025-01-24 02:42:11 +0100 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) hackager |
| 2025-01-24 02:41:19 +0100 | haskellbridge | (~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection) |
| 2025-01-24 02:04:28 +0100 | avalan | (~dweller@178.62.146.60) (Remote host closed the connection) |
| 2025-01-24 02:04:28 +0100 | beastwick | (~brian@user/beastwick) (Remote host closed the connection) |
| 2025-01-24 02:00:49 +0100 | dweller | (~dweller@178.62.146.60) dwelli |
| 2025-01-24 02:00:48 +0100 | beastwic1 | (~brian@pool-74-102-103-193.nwrknj.fios.verizon.net) |
| 2025-01-24 00:22:26 +0100 | Miroboru | (~myrvoll@178-164-114.82.3p.ntebredband.no) Miroboru |
| 2025-01-24 00:21:06 +0100 | Miroboru | (~myrvoll@178-164-114.82.3p.ntebredband.no) (Ping timeout: 276 seconds) |
| 2025-01-24 00:13:55 +0100 | catman | (~catman@user/catman) catman |
| 2025-01-24 00:08:20 +0100 | catman | (~catman@user/catman) (Quit: WeeChat 4.5.1) |
| 2025-01-23 23:46:16 +0100 | tv | (~tv@user/tv) (Read error: Connection reset by peer) |
| 2025-01-23 20:20:23 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-01-23 19:58:57 +0100 | Guest12 | (~Guest12@2a02:2f0f:6109:3500:6bf:1bff:fec0:9354) (Quit: Client closed) |
| 2025-01-23 18:36:40 +0100 | <geekosaur> | also other things which assume that, since xmonad "has two screens available", they're both visible |
| 2025-01-23 18:35:08 +0100 | <geekosaur> | it's relatively easy to do that. the first problem is convincing xmonad it has more than one screen when it doesn't (IndependentScreens does this, but not the way you want), the second is needing to edit the StackSet to switch your fake "screens", the third is convincing e.g. "refresh" not to try to display both screens when they're not actually separate |
| 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. |