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