2023/07/22

2023-07-22 01:43:39 +0200Lears(~Leary]@user/Leary/x-0910699) (Remote host closed the connection)
2023-07-22 01:43:53 +0200[Leary](~Leary]@user/Leary/x-0910699)
2023-07-22 03:01:04 +0200hightower2(~hightower@213-202-64-66.dsl.iskon.hr) (Read error: Connection reset by peer)
2023-07-22 03:02:34 +0200hightower2(~hightower@141-136-238-132.dsl.iskon.hr)
2023-07-22 03:40:32 +0200ft(~ft@p508db1fa.dip0.t-ipconnect.de) (Ping timeout: 240 seconds)
2023-07-22 03:42:38 +0200ft(~ft@p508db95a.dip0.t-ipconnect.de)
2023-07-22 04:24:06 +0200td_(~td@i5387091C.versanet.de) (Ping timeout: 252 seconds)
2023-07-22 04:25:59 +0200td_(~td@i53870914.versanet.de)
2023-07-22 06:12:35 +0200 <galactic_starfis> Apparently not, though your answer is the XMonad way to do it... and it totally kicks butt, so...
2023-07-22 06:12:40 +0200 <galactic_starfis> who knows what they're on/after
2023-07-22 06:12:42 +0200 <galactic_starfis> ¯\_(ツ)_/¯
2023-07-22 06:44:04 +0200 <absta[m]> Hmm, I never once experienced dbus not starting
2023-07-22 08:45:00 +0200immibis(~quassel@2a01:4f9:4a:4caf::2)
2023-07-22 10:06:37 +0200 <geekosaur> some display managers autostart it, some distros autostart it with X
2023-07-22 10:06:47 +0200 <geekosaur> others you have to do it manually
2023-07-22 10:08:51 +0200 <geekosaur> and I think they were looking for a more Windows-like answer, but yeh, that's not what you get with xmonad
2023-07-22 10:09:45 +0200 <geekosaur> you could get it with something like the xmonad under MATE setup I have, but that gets you a Windows-like REGEDIT setup too :) (dconf-editor to configure xmonad as the wm)
2023-07-22 11:04:15 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-22 11:06:54 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-22 11:56:39 +0200tremon(~tremon@83.80.159.219)
2023-07-22 11:59:43 +0200 <xmonadtrack> New branch created: pull/463 (2 commits) https://github.com/xmonad/xmonad/pull/463
2023-07-22 11:59:57 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-22 12:00:11 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-22 13:55:41 +0200hightower2(~hightower@141-136-238-132.dsl.iskon.hr) (Ping timeout: 244 seconds)
2023-07-22 15:05:22 +0200 <gar[m]> Is xmonad compatible with ewmh https://github.com/polybar/polybar/wiki/Module:-xworkspaces
2023-07-22 15:09:28 +0200 <geekosaur> configure XMonad.Hooks.EwmhDesktops in your config
2023-07-22 18:11:39 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-22 18:11:39 +0200unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-22 18:25:58 +0200ml|(~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds)
2023-07-22 18:39:51 +0200ml|(~ml|@user/ml/x-5298235)
2023-07-22 20:40:42 +0200srk_(~sorki@user/srk)
2023-07-22 20:43:29 +0200srk(~sorki@user/srk) (Ping timeout: 246 seconds)
2023-07-22 20:43:31 +0200srk_srk
2023-07-22 20:47:31 +0200redirtestcabal(~redirtest@069-135-003-034.biz.spectrum.com)
2023-07-22 20:47:53 +0200redirtestcabal(~redirtest@069-135-003-034.biz.spectrum.com) (Client Quit)
2023-07-22 20:54:21 +0200 <geekosaur> I… what was that doing here?
2023-07-22 20:54:39 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-22 20:54:54 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-22 20:55:15 +0200 <geekosaur> oh, apparently kiwiirc was being "helpful" and remembered it from some other connection
2023-07-22 20:55:43 +0200 <geekosaur> (I was testing whether #haskell-cabal would forward to #hackage)
2023-07-22 20:56:15 +0200 <Solid> huh?
2023-07-22 20:56:24 +0200 <geekosaur> [22 18:47:31] * redirtestcabal (~redirtest@069-135-003-034.biz.spectrum.com) has joined
2023-07-22 20:57:04 +0200 <geekosaur> at first I thought somehow the forward-ban ended up pointing here instead of #hackage
2023-07-22 21:15:44 +0200T_X_(~T_X@diktynna.open-mesh.org)
2023-07-22 21:16:16 +0200T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2023-07-22 21:18:59 +0200 <Solid> ah
2023-07-22 21:19:15 +0200 <Solid> at some point I just configured my IRC client to ignore all of that join/leave noise
2023-07-22 21:19:25 +0200 <Solid> Only downside is that I'm now oblivious to netsplits :)
2023-07-22 21:25:36 +0200 <geekosaur> we don't see many of those anyway
2023-07-22 21:25:54 +0200 <geekosaur> closest we get i when the matrix or irccloud bridges fall over
2023-07-22 21:25:58 +0200 <geekosaur> *is
2023-07-22 21:45:17 +0200lain1001(~lain@76.108.135.43)
2023-07-22 23:03:16 +0200Waffelo[m](~waffelodr@2001:470:69fc:105::3:86d0) ()
2023-07-22 23:03:27 +0200fr1d4y[m](~fr1d4yenv@2001:470:69fc:105::2:ea3c)