2021-05-24 23:02:46 +0200triskai(~relikt@216-164-151-15.s8205.c3-0.atw-cbr1.atw.pa.cable.rcncustomer.com) (Read error: Connection reset by peer)
2021-05-24 23:31:00 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-24 23:31:27 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 264 seconds)
2021-05-24 23:58:09 +0200seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-05-25 00:32:21 +0200themc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-05-25 00:45:43 +0200qbt(~edun@user/edun) (Quit: WeeChat 3.1)
2021-05-25 00:45:52 +0200themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-25 00:46:10 +0200themainman(~themainma@user/themainman)
2021-05-25 02:25:40 +0200wz1000_(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 02:25:53 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Ping timeout: 264 seconds)
2021-05-25 02:28:01 +0200fizzie(fis@selene.zem.fi) (Ping timeout: 264 seconds)
2021-05-25 02:29:08 +0200fizzie(fis@selene.zem.fi)
2021-05-25 03:18:21 +0200themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-25 03:43:14 +0200Viking667(viking@124.197.53.238)
2021-05-25 03:43:38 +0200 <Viking667> ...uh... I thought you lot were all meant to be over here living it up large while FN burned down
2021-05-25 04:38:34 +0200td__(~td@94.134.91.149) (Ping timeout: 264 seconds)
2021-05-25 04:40:03 +0200td_(~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 05:04:58 +0200boxscape(~boxscape@user/boxscape) (Ping timeout: 264 seconds)
2021-05-25 06:39:17 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 272 seconds)
2021-05-25 06:42:19 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 07:03:11 +0200 <dmwit> Viking667: Sounds right.
2021-05-25 07:03:44 +0200 <dmwit> vrs: That's against freenode rules now. Censorship, man
2021-05-25 07:16:58 +0200abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 264 seconds)
2021-05-25 07:36:45 +0200 <Solid> Once we have OP here we should just set +f ##xmonad-has-moved-to-libera or something
2021-05-25 07:37:05 +0200 <Solid> *set that on freenode
2021-05-25 08:02:16 +0200qbt(~edun@user/edun)
2021-05-25 08:09:18 +0200qbt(~edun@user/edun) (Read error: Connection reset by peer)
2021-05-25 08:11:04 +0200qbt(~edun@user/edun)
2021-05-25 08:15:21 +0200wonko(~wjc@62.115.229.50)
2021-05-25 09:16:32 +0200 <Solid> liskin: I was just now looking into #410 again (removing deprecated things); the dbus package for haskell pulls in _a lot_ of dependencies, I'm not sure we want that for xmonad core
2021-05-25 09:17:53 +0200wz1000_wz1000
2021-05-25 09:18:05 +0200 <Solid> then I saw that alacritty aggressively wants me to remove deprecations (with a popup on startup as well)
2021-05-25 09:18:09 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Quit: WeeChat 2.8)
2021-05-25 09:18:21 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 09:18:34 +0200 <Solid> I'm left to wonder whether the xmessage solution would really be that bad; how often do people realistically recompile their xmonad configs?
2021-05-25 09:18:51 +0200 <Solid> *people who would get annoyed at these messages beause they want to fix this in 6 months time
2021-05-25 09:19:09 +0200 <Viking667> I normally edit xmonad.hs instead and restart instead of recompiling, I guess that's a different use case.
2021-05-25 09:20:02 +0200 <Solid> Viking667: that _is_ recompiling :)
2021-05-25 09:20:36 +0200 <vrs> I'd kind of like a version of xmessage that displays unicode properly
2021-05-25 09:21:53 +0200 <Viking667> Solid: so what's "xmonad --restart" then?
2021-05-25 09:22:09 +0200 <Viking667> Because that's what I use, and is what is inside my xmonad.hs
2021-05-25 09:22:25 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Client Quit)
2021-05-25 09:25:34 +0200 <Solid> Viking667: you really mean xmonad --restart without invoking xmonad --recompile first? I fail to see how changes to your xmonad config would take effect then
2021-05-25 09:27:13 +0200wz1000(~zubin@2a01:4f8:1c0c:40d9::1)
2021-05-25 09:28:06 +0200wz1000(~zubin@2a01:4f8:1c0c:40d9::1) (Client Quit)
2021-05-25 09:28:15 +0200wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 09:29:17 +0200 <Viking667> From what I understand, xmonad --restart re-reads the xmonad.hs on invocation, therefore I get the changes I want. The modules compiled INTO xmonad by the --recompile process aren't changing, after all.
2021-05-25 09:29:48 +0200 <Viking667> If I were to remove/add module names from the .hs, then yes I'd probably think about a --recompile
2021-05-25 09:37:59 +0200 <Solid> what I'm saying is that you define xmonad's main function inside your xmonad.hs
2021-05-25 09:38:14 +0200 <Solid> It's not a config file that is just read and then incorporated into the program
2021-05-25 09:38:19 +0200 <Solid> it is the starting point of the program
2021-05-25 09:38:55 +0200 <Solid> I just saw that we are doing a check on startup though, which means that xmonad --restart _will_ recompile your config, just after doing the restart
2021-05-25 09:39:45 +0200 <Solid> If you have an .xsession.log or similar you'll probably find compilation messages there
2021-05-25 09:43:01 +0200 <Viking667> hm. Figures. I clearly missed that.
2021-05-25 09:58:01 +0200Viking667(viking@124.197.53.238) (Quit: *croak*)
2021-05-25 09:58:34 +0200Viking667(viking@124.197.53.238)
2021-05-25 10:12:21 +0200mc47(~yecinem@89.246.239.190)
2021-05-25 10:15:24 +0200dmwit_(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net)
2021-05-25 10:15:43 +0200dmwit(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net) (Ping timeout: 264 seconds)
2021-05-25 10:17:38 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 10:19:46 +0200joshproehl(~quassel@dtools-d10-tx-1.inf.daedalusdreams.com)
2021-05-25 10:20:26 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 252 seconds)
2021-05-25 10:24:19 +0200Viking667(viking@124.197.53.238) (*.net *.split)
2021-05-25 10:24:19 +0200wonko(~wjc@62.115.229.50) (*.net *.split)
2021-05-25 10:24:19 +0200qbt(~edun@user/edun) (*.net *.split)
2021-05-25 10:24:19 +0200td_(~td@muedsl-82-207-238-005.citykom.de) (*.net *.split)
2021-05-25 10:24:19 +0200eyenx(~eyenxeyen@eyenx.ch) (*.net *.split)
2021-05-25 10:24:19 +0200joshproehl_(~quassel@dtools-d10-tx-1.inf.daedalusdreams.com) (*.net *.split)
2021-05-25 10:24:43 +0200td_(~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 10:26:11 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 244 seconds)
2021-05-25 10:27:54 +0200wonko(~wjc@62.115.229.50)
2021-05-25 10:27:54 +0200qbt(~edun@user/edun)
2021-05-25 10:27:54 +0200eyenx(~eyenxeyen@eyenx.ch)
2021-05-25 10:29:28 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 10:37:21 +0200 <liskin> Solid: we can just use notify-send and fallback to xmessage
2021-05-25 10:37:40 +0200 <liskin> unfortunately notify-send doesn't seem to indicate whether it was able to send the notification or not :-)
2021-05-25 10:37:41 +0200 <liskin> :-(
2021-05-25 10:42:05 +0200 <liskin> it's a bit weird actually, the source code seems to handle it correctly, but when I stop and mask dunst.service, it doesn't fail :-/
2021-05-25 10:42:42 +0200 <liskin> perhaps it would fail if I never had any dunst in the first place
2021-05-25 10:45:04 +0200 <Solid> doesn't report anything for me eitehr
2021-05-25 10:45:10 +0200 <Solid> and I don't use a notification daemon at all
2021-05-25 10:48:31 +0200 <liskin> oh, possibly it's becase no one checks the return value of https://sources.debian.org/src/libnotify/0.7.9-3/tools/notify-send.c/#L278
2021-05-25 10:56:11 +0200Bruners(lasseb@colargol.tihlde.org)
2021-05-25 10:59:14 +0200themainman(~themainma@user/themainman)
2021-05-25 11:04:22 +0200eyenx(~eyenxeyen@eyenx.ch) (Ping timeout: 264 seconds)
2021-05-25 11:05:40 +0200eyenx(~eyenxeyen@eyenx.ch)
2021-05-25 11:49:58 +0200 <mc47> Solid, liskin: do you have any ressources I can read to understand what the hell is going on in #547 and #294? The extensible config stuff
2021-05-25 11:50:33 +0200 <mc47> The type-level trickery intrigued me and I don't know where to read more about it
2021-05-25 11:51:38 +0200 <liskin> mc47: I don't have anything in particular that I'd recommend reading.
2021-05-25 11:52:04 +0200 <liskin> As usual, I lived through the evolution and just happen to know this stuff without having the slightest idea where that knowledge came from :-/
2021-05-25 11:52:49 +0200 <liskin> but googling "haskell typeable" gives me a couple blog posts that I'd expect to be more or less correct/meaningful
2021-05-25 11:53:31 +0200 <liskin> tldr is that Typeable lets you do dynamically typed values safely
2021-05-25 11:54:11 +0200 <liskin> the compiler generates instances of Typeable, which let you convert any type a into a Maybe specific type you want
2021-05-25 11:55:36 +0200 <mc47> that sounds really interesting, I'll check that out
2021-05-25 11:55:56 +0200 <mc47> Experiencing the evolution first-hand is really nice
2021-05-25 11:58:05 +0200 <liskin> it isn't the most cost effective way of learning stuff though
2021-05-25 11:58:32 +0200 <mc47> yes, but I think it gives a better insight
2021-05-25 12:01:45 +0200 <liskin> as long as you don't forget stuff :-)
2021-05-25 12:04:32 +0200 <Solid> one thing to be aware of is that people who talk about TypeRep can mean two different things (indexed vs. not indexed)
2021-05-25 12:04:51 +0200 <Solid> because we have Data.Typeable.TypeRep and Type.Reflection.TypeRep