Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,199 events total
2025-10-01 00:18:44 <haskellbridge> <iqubic (she/her)> The more I think about it, the less I actually want this.
2025-10-01 01:29:47 <haskellbridge> <iqubic (she/her)> If I use XMonad.StackSet.Screens, what order will the screens be returned in?
2025-10-01 01:32:51 <haskellbridge> <iqubic (she/her)> The source shows this: screens s = current s : visible s
2025-10-01 01:32:59 <haskellbridge> <iqubic (she/her)> but how is visible sorted?
2025-10-01 01:41:25 <geekosaur> I don't think there's a guarantee; generally it works out to MRU
2025-10-01 01:42:14 <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 <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 <haskellbridge> <iqubic (she/her)> I thought I did, but it turns out I don't.
2025-10-01 01:44:34 <geekosaur> (for greedyview current and the original visible entry are swapped, so indeed order can end up weird)
2025-10-01 01:45:02 <haskellbridge> <iqubic (she/her)> Yeah, I understand that now.
2025-10-01 01:46:26 <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 × terrorjack quits (~terrorjac@2a01:4f8:c17:9d11::) (Quit: The Lounge - https://thelounge.chat)
2025-10-01 02:45:29 terrorjack joins (~terrorjac@static.121.247.201.138.clients.your-server.de)
2025-10-01 02:45:46 × td_ quits (~td@i5387093E.versanet.de) (Ping timeout: 248 seconds)
2025-10-01 02:47:37 td_ joins (~td@i5387093A.versanet.de)
2025-10-01 03:11:22 × berberman quits (~berberman@user/berberman) (Ping timeout: 248 seconds)
2025-10-01 03:11:51 berberman joins (~berberman@user/berberman)
2025-10-01 04:16:31 × gwentpl quits (~gwpl@user/gwentpl) (Ping timeout: 240 seconds)
2025-10-01 04:25:52 <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 gwentpl joins (~gwpl@user/gwentpl)
2025-10-01 04:50:35 <haskellbridge> <iqubic (she/her)> Well, if it's not visible and has no windows.
2025-10-01 04:51:28 <haskellbridge> <iqubic (she/her)> Because visible and has windows would show up I assume!
2025-10-01 04:56:35 <geekosaur> if it has a tag (name), it will show up
2025-10-01 04:56:53 <geekosaur> and omce it's there, something would have to explicitly delete it for it to go away
2025-10-01 05:28:09 <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 <geekosaur> yes
2025-10-01 05:29:10 <haskellbridge> <iqubic (she/her)> I see.
2025-10-01 06:22:36 Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213)
2025-10-01 06:25:50 × gauge quits (~gauge@user/gauge) (Read error: Connection reset by peer)
2025-10-01 06:31:33 gauge joins (~gauge@user/gauge)
2025-10-01 06:39:37 <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 × gwentpl quits (~gwpl@user/gwentpl) (Ping timeout: 240 seconds)
2025-10-01 06:41:59 gwentpl joins (~gwpl@user/gwentpl)
2025-10-01 06:47:40 Solid joins (~slot@xmonad/slotThe)
2025-10-01 06:49:18 × Enrico63 quits (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed)
2025-10-01 08:25:33 × ft quits (~ft@p4fc2a225.dip0.t-ipconnect.de) (Quit: leaving)
2025-10-01 09:23:29 × gwentpl quits (~gwpl@user/gwentpl) (Ping timeout: 260 seconds)
2025-10-01 09:23:57 gwentpl joins (~gwpl@user/gwentpl)
2025-10-01 09:29:12 spwl joins (~gwpl@user/gwentpl)
2025-10-01 09:29:55 × gwentpl quits (~gwpl@user/gwentpl) (Read error: Connection reset by peer)
2025-10-01 10:12:21 × redgloboli quits (~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2025-10-01 10:13:58 redgloboli joins (~redglobol@user/redgloboli)
2025-10-01 15:12:43 × Solid quits (~slot@xmonad/slotThe) (Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50))
2025-10-01 15:16:33 × haskellbridge quits (~hackager@syn-096-028-224-214.res.spectrum.com) (Remote host closed the connection)
2025-10-01 15:20:22 haskellbridge joins (~hackager@syn-096-028-224-214.res.spectrum.com)
2025-10-01 16:38:00 tccq joins (~user@user/tccq)
2025-10-01 17:39:22 ft joins (~ft@p4fc2a225.dip0.t-ipconnect.de)
2025-10-01 22:46:17 rascasse joins (rascasse@user/diep)
2025-10-01 23:46:26 hightower3 joins (~hightower@213.186.15.36)
2025-10-01 23:46:36 srk_ joins (~sorki@user/srk)
2025-10-01 23:47:57 × srk quits (~sorki@user/srk) (Remote host closed the connection)
2025-10-01 23:48:58 × hightower2 quits (~hightower@213.186.15.36) (Read error: Connection reset by peer)
2025-10-01 23:49:27 srk_ is now known as srk
2025-10-01 23:51:28 × tccq quits (~user@user/tccq) (Remote host closed the connection)
2025-10-02 01:24:18 × rascasse quits (rascasse@user/diep) (Remote host closed the connection)
2025-10-02 02:45:20 × td_ quits (~td@i5387093A.versanet.de) (Ping timeout: 240 seconds)
2025-10-02 02:47:19 td_ joins (~td@i53870901.versanet.de)
2025-10-02 06:50:18 × ft quits (~ft@p4fc2a225.dip0.t-ipconnect.de) (Quit: leaving)
2025-10-02 07:13:27 tema joins (~tema@93.175.2.220)
2025-10-02 07:13:45 × tema quits (~tema@93.175.2.220) (Client Quit)
2025-10-02 07:15:57 Solid joins (~slot@xmonad/slotThe)
2025-10-02 09:24:59 Maeda joins (~Maeda@91-161-10-149.subs.proxad.net)
2025-10-02 09:29:34 Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213)
2025-10-02 09:29:38 <Maeda> Hi there! Do spawnOnce (from XMonad.Util.SpawnOnce) not honoring a ManagedHook where a rule for a window className to be "insertPosition Below Newer"? For example, closing that window opened at logon and re-opening it makes the 'Below Newer' rule effective as expected (and any further opening of that windows is OK).
2025-10-02 09:40:37 × Digit quits (~user@user/digit) (Remote host closed the connection)
2025-10-02 09:45:10 Digit joins (~user@user/digit)
2025-10-02 10:43:27 × Enrico63 quits (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed)
2025-10-02 11:52:21 mc47 joins (~yecinem@host-212-114-138-22.customer.m-online.net)
2025-10-02 11:52:40 × mc47 quits (~yecinem@host-212-114-138-22.customer.m-online.net) (Changing host)
2025-10-02 11:52:40 mc47 joins (~yecinem@xmonad/TheMC47)
2025-10-02 13:22:21 Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213)
2025-10-02 13:29:03 × Enrico63 quits (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed)
2025-10-02 13:31:04 Enrico63 joins (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213)
2025-10-02 13:33:27 <Enrico63> Hi there. I'd like some help debugging an issue with a project of mine. The reason I'd like to ask here is that I can reproduce the bug when logging out of xmonad and back in again. I don't think the bug is in xmonad but in the xmobar status bar, however for obvious reasons I think I can get some help here. I suppose it's a bit OT, but can I ask?
2025-10-02 13:34:02 <Enrico63> (obviously the bug could be in my project as well, obviously)
2025-10-02 13:35:17 <Enrico63> The issue has to do with a zombie process left running when logging out of xmonad, I think because it shuts xmobar down which in turns is supposed to shut my plugin down
2025-10-02 13:52:33 × PotatoGim quits (sid99505@id-99505.lymington.irccloud.com) (Ping timeout: 252 seconds)
2025-10-02 13:56:39 PotatoGim joins (sid99505@id-99505.lymington.irccloud.com)
2025-10-02 14:02:37 Solid` joins (~slot@uhh-wlan-fo-134-100-17-67.rrz.uni-hamburg.de)
2025-10-02 14:04:13 × Solid quits (~slot@xmonad/slotThe) (Ping timeout: 264 seconds)
2025-10-02 14:22:39 × Solid` quits (~slot@uhh-wlan-fo-134-100-17-67.rrz.uni-hamburg.de) (Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50))
2025-10-02 14:23:56 <geekosaur> Maeda, it should be honored but insertPosition plays games with the StackSet and can conflict with a lot of things if done in the wrong order. Try moving that rule relative to manageSpawn
2025-10-02 14:32:41 <Enrico63> Ok, let me rephrase the question.
2025-10-02 14:32:41 <Enrico63> Here's the `main` in my `xmonad.hs`:
2025-10-02 14:32:42 <Enrico63> ```
2025-10-02 14:32:42 <Enrico63> main :: IO ()
2025-10-02 14:32:43 <Enrico63> main = xmonad
2025-10-02 14:32:43 <Enrico63>      . ewmhFullscreen
2025-10-02 14:32:44 <Enrico63>      . ewmh
2025-10-02 14:32:44 <Enrico63>      . withEasySB (statusBarProp "xmobar ~/.config/xmobar/xmobar.hs" (clickablePP myXmobarPP)) toggleStrutsKey
2025-10-02 14:32:45 <Enrico63>      $ myConfig
2025-10-02 14:32:45 <Enrico63>      where
2025-10-02 14:32:46 <Enrico63>        toggleStrutsKey XConfig { modMask = m } = (m, xK_b)
2025-10-02 14:32:46 <Enrico63> ```
2025-10-02 14:32:47 <Enrico63> What do I know, from this, about what happens to the executable xmobar when I log out of xmonad? How is it shut down? Just like if I had done `kill $(pidof xmobar)`? Or `kill -KILL $(pidof xmobar)`? Or what?
2025-10-02 14:43:00 <liskin> Enrico63: depends on what "log out of xmonad" means exactly but most likely nothing happens whatsoever
2025-10-02 14:43:02 <geekosaur> https://hackage.haskell.org/package/xmonad-contrib-0.18.1/docs/XMonad-Hooks-StatusBar.html#v:killStatusBar
2025-10-02 14:43:28 <liskin> There's no hook when xmonad exits so this function won't be called unless you do it yourself
2025-10-02 14:43:51 <liskin> (iirc)
2025-10-02 14:44:11 × Enrico63 quits (~Enrico63@2a0b:e541:10d0:0:9efc:e8ff:fe24:3213) (Quit: Client closed)

All times are in UTC.