2025/10/01

2025-10-01 00:10:06 +0000 <haskellbridge> <iqubic (she/her)> I'm not sure why that needs two arguments there. Can't you just do it with say, an offset from the top-left corner of the new window?
2025-10-01 00:11:37 +0000 <geekosaur> it actually computes an offset based on where the pointer was initially. the `(0,0)` in the example says not to take the original position into account
2025-10-01 00:12:20 +0000 <haskellbridge> <iqubic (she/her)> Why would you want that?
2025-10-01 00:12:36 +0000 <geekosaur> I have no idea; I didn't write it
2025-10-01 00:15:36 +0000 <geekosaur> (I personally don't know why anyone would want to auto-move the pointer…)
2025-10-01 00:18:44 +0000 <haskellbridge> <iqubic (she/her)> The more I think about it, the less I actually want this.
2025-10-01 01:29:47 +0000 <haskellbridge> <iqubic (she/her)> If I use XMonad.StackSet.Screens, what order will the screens be returned in?
2025-10-01 01:32:51 +0000 <haskellbridge> <iqubic (she/her)> The source shows this: screens s = current s : visible s
2025-10-01 01:32:59 +0000 <haskellbridge> <iqubic (she/her)> but how is visible sorted?
2025-10-01 01:41:25 +0000 <geekosaur> I don't think there's a guarantee; generally it works out to MRU
2025-10-01 01:42:14 +0000 <geekosaur> (if you `view` a workspace already in `visible`, `current` is pushed on top of `visible` and then set to the selected workspace)
2025-10-01 01:43:00 +0000 <haskellbridge> <iqubic (she/her)> Yeah, that's fine. For what I'm doing, I don't actually need a specific guaranteed order.
2025-10-01 01:43:15 +0000 <haskellbridge> <iqubic (she/her)> I thought I did, but it turns out I don't.
2025-10-01 01:44:34 +0000 <geekosaur> (for greedyview current and the original visible entry are swapped, so indeed order can end up weird)
2025-10-01 01:45:02 +0000 <haskellbridge> <iqubic (she/her)> Yeah, I understand that now.
2025-10-01 01:46:26 +0000 <haskellbridge> <iqubic (she/her)> Also, I found X.U.Logger in contrib and the screen specific loggers mostly do what I want, and for the other stuff, I can just use the source code as a guide.
2025-10-01 02:42:52 +0000terrorjack(~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat)
2025-10-01 02:45:29 +0000terrorjack(~terrorjac@static.121.247.201.138.clients.your-server.de) terrorjack
2025-10-01 02:45:46 +0000td_(~td@i5387093E.versanet.de) (Ping timeout: 248 seconds)
2025-10-01 02:47:37 +0000td_(~td@i5387093A.versanet.de) td_
2025-10-01 03:11:22 +0000berberman(~berberman@user/berberman) (Ping timeout: 248 seconds)
2025-10-01 03:11:51 +0000berberman(~berberman@user/berberman) berberman
2025-10-01 04:16:31 +0000gwentpl(~gwpl@user/gwentpl) (Ping timeout: 240 seconds)
2025-10-01 04:25:52 +0000 <haskellbridge> <iqubic (she/her)> If a workspace has no window on it, will it be present in the StackSet that XMonad.Core.withWindowSet gives me?
2025-10-01 04:28:12 +0000gwentpl(~gwpl@user/gwentpl) gwentpl
2025-10-01 04:50:35 +0000 <haskellbridge> <iqubic (she/her)> Well, if it's not visible and has no windows.
2025-10-01 04:51:28 +0000 <haskellbridge> <iqubic (she/her)> Because visible and has windows would show up I assume!
2025-10-01 04:56:35 +0000 <geekosaur> if it has a tag (name), it will show up
2025-10-01 04:56:53 +0000 <geekosaur> and omce it's there, something would have to explicitly delete it for it to go away
2025-10-01 05:28:09 +0000 <haskellbridge> <iqubic (she/her)> What does a hidden workspace mean in this context? Is that just a workspace that's not visible on any monitors?
2025-10-01 05:28:32 +0000 <geekosaur> yes
2025-10-01 05:29:10 +0000 <haskellbridge> <iqubic (she/her)> I see.
2025-10-01 06:22:36 +0000Enrico63(~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) Enrico63
2025-10-01 06:25:50 +0000gauge(~gauge@user/gauge) (Read error: Connection reset by peer)
2025-10-01 06:31:33 +0000gauge(~gauge@user/gauge) gauge
2025-10-01 06:39:37 +0000 <haskellbridge> <Solid> iqubic (she/her): Well, what different information do you want to show? I guess the bars already show the windows on the respective workspaces, and also the focus etc, right?
2025-10-01 06:41:19 +0000gwentpl(~gwpl@user/gwentpl) (Ping timeout: 240 seconds)
2025-10-01 06:41:59 +0000gwentpl(~gwpl@user/gwentpl) gwentpl
2025-10-01 06:47:40 +0000Solid(~slot@xmonad/slotThe) slot
2025-10-01 06:49:18 +0000Enrico63(~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed)
2025-10-01 08:25:33 +0000ft(~ft@p4fc2a225.dip0.t-ipconnect.de) (Quit: leaving)
2025-10-01 09:23:29 +0000gwentpl(~gwpl@user/gwentpl) (Ping timeout: 260 seconds)
2025-10-01 09:23:57 +0000gwentpl(~gwpl@user/gwentpl) gwentpl
2025-10-01 09:29:12 +0000spwl(~gwpl@user/gwentpl) gwentpl
2025-10-01 09:29:55 +0000gwentpl(~gwpl@user/gwentpl) (Read error: Connection reset by peer)
2025-10-01 10:12:21 +0000redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2025-10-01 10:13:58 +0000redgloboli(~redglobol@user/redgloboli) redgloboli
2025-10-01 15:12:43 +0000Solid(~slot@xmonad/slotThe) (Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50))
2025-10-01 15:16:33 +0000haskellbridge(~hackager@syn-096-028-224-214.res.spectrum.com) (Remote host closed the connection)
2025-10-01 15:20:22 +0000haskellbridge(~hackager@syn-096-028-224-214.res.spectrum.com) hackager
2025-10-01 16:38:00 +0000tccq(~user@user/tccq) tccq
2025-10-01 17:39:22 +0000ft(~ft@p4fc2a225.dip0.t-ipconnect.de) ft
2025-10-01 22:46:17 +0000rascasse(rascasse@user/diep) diep
2025-10-01 23:46:26 +0000hightower3(~hightower@213.186.15.36) hightower2
2025-10-01 23:46:36 +0000srk_(~sorki@user/srk) srk
2025-10-01 23:47:57 +0000srk(~sorki@user/srk) (Remote host closed the connection)
2025-10-01 23:48:58 +0000hightower2(~hightower@213.186.15.36) (Read error: Connection reset by peer)
2025-10-01 23:49:27 +0000srk_srk
2025-10-01 23:51:28 +0000tccq(~user@user/tccq) (Remote host closed the connection)