Newest at the top
| 2024-06-25 04:52:21 +0200 | td_ | (~td@i53870933.versanet.de) |
| 2024-06-25 04:50:35 +0200 | Leary | (~Leary@user/Leary/x-0910699) |
| 2024-06-25 04:50:26 +0200 | td_ | (~td@i5387092F.versanet.de) (Ping timeout: 256 seconds) |
| 2024-06-25 04:48:35 +0200 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) |
| 2024-06-25 04:44:30 +0200 | terrorjack | (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 2024-06-25 02:57:21 +0200 | <geekosaur> | but many programs might not bother having both paths since it has to fall back to XQueryTree if _NET_CLIENT_LIST isn't in _NET_SUPPORTED or not present on the root window |
| 2024-06-25 02:56:22 +0200 | <geekosaur> | actually it looks like it can get a window list from _NET_CLIENT_LIST on the root window, but it still has to query them for _NET_WM_DESKTOP to see where they are |
| 2024-06-25 02:46:58 +0200 | <haskellbridge> | <iqubic (she/her)> From what I'm seeing in the polybar source, it seems to use the XQueryTree. |
| 2024-06-25 02:46:19 +0200 | <haskellbridge> | <iqubic (she/her)> I see. |
| 2024-06-25 02:46:01 +0200 | <geekosaur> | when you use xmonad's PP instead of EWMH, xmonad can query the Stack of each workspace; programs that use EWMH have to use XQueryTree and then query every top level window returned |
| 2024-06-25 02:44:40 +0200 | <geekosaur> | it's kinda backwards. there's no mater list; every client has a _NET_WM_DESKTOP with the EWMH workspace number (index into _NET_DESKTOP_NAMES) as its value |
| 2024-06-25 02:39:52 +0200 | <haskellbridge> | <iqubic (she/her)> Is there just some property of the root window I can query? |
| 2024-06-25 02:39:37 +0200 | <haskellbridge> | <iqubic (she/her)> How exactly does ewmh work? How does xmonad set which workspaces have windows on them? |
| 2024-06-25 02:06:59 +0200 | mekeor | (~user@2001:a61:25ed:a301:ad37:1d69:745f:dbe2) (Quit: bad [...] major browsers) |
| 2024-06-25 01:25:40 +0200 | mekeor` | mekeor |
| 2024-06-25 01:22:27 +0200 | mekeor | (~user@2001:a61:24d2:9401:96ac:ce90:6d78:efe3) (Ping timeout: 264 seconds) |
| 2024-06-25 01:21:01 +0200 | mekeor` | (~user@2001:a61:25ed:a301:ad37:1d69:745f:dbe2) |
| 2024-06-24 21:49:44 +0200 | <haskellbridge> | <lush> thanks! |
| 2024-06-24 21:49:41 +0200 | <haskellbridge> | and it works for me too now, I realised that I made a stupid mistake in my config... |
| 2024-06-24 21:49:41 +0200 | <haskellbridge> | <lush> yeah, I intend mod-s return |
| 2024-06-24 21:48:55 +0200 | <geekosaur> | just to be certain, you intend mod-s return, not mod-shift-return? |
| 2024-06-24 21:44:46 +0200 | <geekosaur> | seems to work here |
| 2024-06-24 21:38:37 +0200 | <haskellbridge> | <lush> Is it possible to set a Keybinding to "M-s <Return>"? It doesn't seem to work for me... |
| 2024-06-24 20:46:18 +0200 | <liskin> | (also I don't really have much time besides day job and hobbies) |
| 2024-06-24 20:45:41 +0200 | <liskin> | But I have so many missions I'm unlikely to make much progress on any :-( |
| 2024-06-24 20:45:39 +0200 | <haskellbridge> | <iqubic (she/her)> Ah. Yeah... that makes sense. I just refactored my config to no longer use X.C |
| 2024-06-24 20:45:14 +0200 | <liskin> | If anything, my mission was using ExtensibleConf to make more stuff extensible as is |
| 2024-06-24 20:45:07 +0200 | <geekosaur> | XMonad.Config |
| 2024-06-24 20:45:00 +0200 | <haskellbridge> | <iqubic (she/her)> What is X.C? |
| 2024-06-24 20:44:32 +0200 | <liskin> | I don't think it was me who wanted X.C to go away but yeah they aren't particularly extensible |
| 2024-06-24 20:43:52 +0200 | <liskin> | Blah, touch keyboards, let's try again |
| 2024-06-24 20:43:38 +0200 | <liskin> | Don't |
| 2024-06-24 20:43:34 +0200 | <liskin> | I do |
| 2024-06-24 20:32:30 +0200 | <haskellbridge> | <iqubic (she/her)> I just switched to this, which does the same thing, but now I don't need to remember to add the default hooks! YAY. https://paste.tomsmeding.com/1oFk2cye |
| 2024-06-24 20:21:46 +0200 | <haskellbridge> | <iqubic (she/her)> You're right... I literally don't need it. |
| 2024-06-24 20:19:50 +0200 | <geekosaur> | and misses some things you probably want |
| 2024-06-24 20:19:41 +0200 | <geekosaur> | X.C.Desktop itself in particular doesn't do anything you can't do with a couple combinators |
| 2024-06-24 20:19:15 +0200 | <geekosaur> | Possibly replacing them, but as is they're somewhat problematic, so yes |
| 2024-06-24 20:15:16 +0200 | <haskellbridge> | <iqubic (she/her)> Oh, liskin wants to just remove the desktopConfigs? |
| 2024-06-24 20:14:29 +0200 | <geekosaur> | I think liskin wants them to go away for that reason? |
| 2024-06-24 20:14:24 +0200 | <haskellbridge> | <iqubic (she/her)> There doesn't seem to be a function of the type "mkDesktopConfig :: Layout a => XConfig a -> XConfig a", so I'm having to do it this way. |
| 2024-06-24 20:14:01 +0200 | <geekosaur> | I think we have an open ticket about that |
| 2024-06-24 20:13:53 +0200 | <geekosaur> | yes, that's the problem with the desktop configs |
| 2024-06-24 20:12:12 +0200 | <haskellbridge> | <iqubic (she/her)> See, the example here also requires you to remember to put in all the hooks yourself: https://hackage.haskell.org/package/xmonad-contrib-0.18.0/docs/XMonad-Config-Desktop.html#g:3 |
| 2024-06-24 20:10:58 +0200 | <geekosaur> | I don't fullscreen stuff very often |
| 2024-06-24 20:10:43 +0200 | <geekosaur> | altghough I should move ewmhFullscreen |
| 2024-06-24 20:10:32 +0200 | <geekosaur> | yes, because debugManageHookOn happens to be safe |
| 2024-06-24 20:09:53 +0200 | <haskellbridge> | <iqubic (she/her)> https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L59 |
| 2024-06-24 20:09:52 +0200 | <haskellbridge> | <iqubic (she/her)> You're also doing it before, I think... |
| 2024-06-24 20:09:43 +0200 | <geekosaur> | you don't have to remember to put the hooks from `baseConfig` back in |