Home liberachat/#xmonad: Logs Calendar

Logs on 2023-07-22 (liberachat/#xmonad)

01:01:04 × hightower2 quits (~hightower@213-202-64-66.dsl.iskon.hr) (Read error: Connection reset by peer)
01:02:34 hightower2 joins (~hightower@141-136-238-132.dsl.iskon.hr)
01:40:32 × ft quits (~ft@p508db1fa.dip0.t-ipconnect.de) (Ping timeout: 240 seconds)
01:42:38 ft joins (~ft@p508db95a.dip0.t-ipconnect.de)
02:24:06 × td_ quits (~td@i5387091C.versanet.de) (Ping timeout: 252 seconds)
02:25:59 td_ joins (~td@i53870914.versanet.de)
04:12:35 <galactic_starfis> Apparently not, though your answer is the XMonad way to do it... and it totally kicks butt, so...
04:12:40 <galactic_starfis> who knows what they're on/after
04:12:42 <galactic_starfis> ¯\_(ツ)_/¯
04:44:04 <absta[m]> Hmm, I never once experienced dbus not starting
06:45:00 immibis joins (~quassel@2a01:4f9:4a:4caf::2)
08:06:37 <geekosaur> some display managers autostart it, some distros autostart it with X
08:06:47 <geekosaur> others you have to do it manually
08:08:51 <geekosaur> and I think they were looking for a more Windows-like answer, but yeh, that's not what you get with xmonad
08:09:45 <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)
09:04:15 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
09:06:54 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
09:56:39 tremon joins (~tremon@83.80.159.219)
09:59:43 <xmonadtrack> New branch created: pull/463 (2 commits) https://github.com/xmonad/xmonad/pull/463
09:59:57 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
10:00:11 unclechu joins (~unclechu@2001:470:69fc:105::354)
11:55:41 × hightower2 quits (~hightower@141-136-238-132.dsl.iskon.hr) (Ping timeout: 244 seconds)
13:05:22 <gar[m]> Is xmonad compatible with ewmh https://github.com/polybar/polybar/wiki/Module:-xworkspaces
13:09:28 <geekosaur> configure XMonad.Hooks.EwmhDesktops in your config
16:11:39 × liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
16:11:39 × unclechu quits (~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
16:25:58 × ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds)
16:39:51 ml| joins (~ml|@user/ml/x-5298235)
18:40:42 srk_ joins (~sorki@user/srk)
18:43:29 × srk quits (~sorki@user/srk) (Ping timeout: 246 seconds)
18:43:31 srk_ is now known as srk
18:47:31 redirtestcabal joins (~redirtest@069-135-003-034.biz.spectrum.com)
18:47:53 × redirtestcabal quits (~redirtest@069-135-003-034.biz.spectrum.com) (Client Quit)
18:54:21 <geekosaur> I… what was that doing here?
18:54:39 liskin[m] joins (~liskinmat@2001:470:69fc:105::768)
18:54:54 unclechu joins (~unclechu@2001:470:69fc:105::354)
18:55:15 <geekosaur> oh, apparently kiwiirc was being "helpful" and remembered it from some other connection
18:55:43 <geekosaur> (I was testing whether #haskell-cabal would forward to #hackage)
18:56:15 <Solid> huh?
18:56:24 <geekosaur> [22 18:47:31] * redirtestcabal (~redirtest@069-135-003-034.biz.spectrum.com) has joined
18:57:04 <geekosaur> at first I thought somehow the forward-ban ended up pointing here instead of #hackage
19:15:44 T_X_ joins (~T_X@diktynna.open-mesh.org)
19:16:16 × T_X quits (~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
19:18:59 <Solid> ah
19:19:15 <Solid> at some point I just configured my IRC client to ignore all of that join/leave noise
19:19:25 <Solid> Only downside is that I'm now oblivious to netsplits :)
19:25:36 <geekosaur> we don't see many of those anyway
19:25:54 <geekosaur> closest we get i when the matrix or irccloud bridges fall over
19:25:58 <geekosaur> *is
19:45:17 lain1001 joins (~lain@76.108.135.43)
21:03:16 Waffelo[m] parts (~waffelodr@2001:470:69fc:105::3:86d0) ()
21:03:27 fr1d4y[m] joins (~fr1d4yenv@2001:470:69fc:105::2:ea3c)
22:50:07 <absta[m]> <geekosaur> "some display managers autostart..." <- Interesting, so far both lightdm and sddm seem to support it.
22:50:55 <geekosaur> others might but you might have to edit a config file and restart them
22:51:04 <geekosaur> some others might not
22:51:49 <absta[m]> May I ask what other display managers are out there that can be used with xmonad?
22:53:18 T_X_ is now known as T_X
22:54:03 <geekosaur> gdm (probably autostarts it), wdm, lxdm — just looking quickly at `apt-cache search 'display manager'`; there may be others
22:54:24 <geekosaur> display managers are completely divorced from sessions
22:57:59 <geekosaur> well, no, since they can wrap the sessions in things like `dbus-launch` like we're talking about, but any display manager can start any session type (with some work; xdm/wdm won't run XDG sessions directly and the others need an XDG session wrapper to run ~/.xsession)
23:05:12 <absta[m]> TIL about wdm. Maybe lxdm is lightweight enough to not start dbus session itself..
23:07:11 <geekosaur> there used to be more but many have ceased to exist. KDE used to have its own kdm for example
23:12:22 <geekosaur> I think MATE had mdm for a while too, then switched to lightdm
23:19:05 × tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in)
23:34:46 × lain1001 quits (~lain@76.108.135.43) (Ping timeout: 260 seconds)

All times are in UTC on 2023-07-22.