Newest at the top
| 2025-01-24 18:11:38 +0100 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 265 seconds) |
| 2025-01-24 18:10:49 +0100 | Guest76 | (~Guest76@208.108.184.253) (Client Quit) |
| 2025-01-24 18:09:12 +0100 | Guest76 | (~Guest76@208.108.184.253) |
| 2025-01-24 16:47:42 +0100 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) |
| 2025-01-24 16:41:44 +0100 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 252 seconds) |
| 2025-01-24 15:59:35 +0100 | b34n5_ | (326c9865e2@irc.cheogram.com) |
| 2025-01-24 14:36:17 +0100 | redgloboli | (~redglobol@user/redgloboli) (Quit: ...enter the matrix...) |
| 2025-01-24 14:34:19 +0100 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) |
| 2025-01-24 14:14:26 +0100 | rieper | (~riepernet@2a03:4000:6:f1d6:6885:6fff:fe5a:8933) rieper |
| 2025-01-24 14:13:15 +0100 | rieper | (~riepernet@2a03:4000:6:f1d6:6885:6fff:fe5a:8933) (Quit: No Ping reply in 180 seconds.) |
| 2025-01-24 13:21:12 +0100 | mc47 | (~yecinem@p200300ee0f038d616a75ecb5ce80e61a.dip0.t-ipconnect.de) (Ping timeout: 246 seconds) |
| 2025-01-24 13:03:55 +0100 | ft | (~ft@p508db1ba.dip0.t-ipconnect.de) ft |
| 2025-01-24 12:34:14 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Remote host closed the connection) |
| 2025-01-24 11:15:46 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-01-24 10:35:30 +0100 | tv | (~tv@user/tv) tv |
| 2025-01-24 10:16:03 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Ping timeout: 265 seconds) |
| 2025-01-24 10:11:36 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-01-24 09:05:13 +0100 | catman | (~catman@user/catman) catman |
| 2025-01-24 09:00:05 +0100 | catman | (~catman@user/catman) (Ping timeout: 252 seconds) |
| 2025-01-24 08:56:43 +0100 | mc47 | (~yecinem@p200300ee0f038d616a75ecb5ce80e61a.dip0.t-ipconnect.de) |
| 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) |