2021/05/25

2021-05-25 00:25:40 +0000wz1000_(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 00:25:53 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Ping timeout: 264 seconds)
2021-05-25 00:28:01 +0000fizzie(fis@selene.zem.fi) (Ping timeout: 264 seconds)
2021-05-25 00:29:08 +0000fizzie(fis@selene.zem.fi)
2021-05-25 01:18:21 +0000themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-25 01:43:14 +0000Viking667(viking@124.197.53.238)
2021-05-25 01:43:38 +0000 <Viking667> ...uh... I thought you lot were all meant to be over here living it up large while FN burned down
2021-05-25 02:38:34 +0000td__(~td@94.134.91.149) (Ping timeout: 264 seconds)
2021-05-25 02:40:03 +0000td_(~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 03:04:58 +0000boxscape(~boxscape@user/boxscape) (Ping timeout: 264 seconds)
2021-05-25 04:39:17 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 272 seconds)
2021-05-25 04:42:19 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 05:03:11 +0000 <dmwit> Viking667: Sounds right.
2021-05-25 05:03:44 +0000 <dmwit> vrs: That's against freenode rules now. Censorship, man
2021-05-25 05:16:58 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 264 seconds)
2021-05-25 05:36:45 +0000 <Solid> Once we have OP here we should just set +f ##xmonad-has-moved-to-libera or something
2021-05-25 05:37:05 +0000 <Solid> *set that on freenode
2021-05-25 06:02:16 +0000qbt(~edun@user/edun)
2021-05-25 06:09:18 +0000qbt(~edun@user/edun) (Read error: Connection reset by peer)
2021-05-25 06:11:04 +0000qbt(~edun@user/edun)
2021-05-25 06:15:21 +0000wonko(~wjc@62.115.229.50)
2021-05-25 07:16:32 +0000 <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 07:17:53 +0000wz1000_wz1000
2021-05-25 07:18:05 +0000 <Solid> then I saw that alacritty aggressively wants me to remove deprecations (with a popup on startup as well)
2021-05-25 07:18:09 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Quit: WeeChat 2.8)
2021-05-25 07:18:21 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 07:18:34 +0000 <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 07:18:51 +0000 <Solid> *people who would get annoyed at these messages beause they want to fix this in 6 months time
2021-05-25 07:19:09 +0000 <Viking667> I normally edit xmonad.hs instead and restart instead of recompiling, I guess that's a different use case.
2021-05-25 07:20:02 +0000 <Solid> Viking667: that _is_ recompiling :)
2021-05-25 07:20:36 +0000 <vrs> I'd kind of like a version of xmessage that displays unicode properly
2021-05-25 07:21:53 +0000 <Viking667> Solid: so what's "xmonad --restart" then?
2021-05-25 07:22:09 +0000 <Viking667> Because that's what I use, and is what is inside my xmonad.hs
2021-05-25 07:22:25 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (Client Quit)
2021-05-25 07:25:34 +0000 <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 07:27:13 +0000wz1000(~zubin@2a01:4f8:1c0c:40d9::1)
2021-05-25 07:28:06 +0000wz1000(~zubin@2a01:4f8:1c0c:40d9::1) (Client Quit)
2021-05-25 07:28:15 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 07:29:17 +0000 <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 07:29:48 +0000 <Viking667> If I were to remove/add module names from the .hs, then yes I'd probably think about a --recompile
2021-05-25 07:37:59 +0000 <Solid> what I'm saying is that you define xmonad's main function inside your xmonad.hs
2021-05-25 07:38:14 +0000 <Solid> It's not a config file that is just read and then incorporated into the program
2021-05-25 07:38:19 +0000 <Solid> it is the starting point of the program
2021-05-25 07:38:55 +0000 <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 07:39:45 +0000 <Solid> If you have an .xsession.log or similar you'll probably find compilation messages there
2021-05-25 07:43:01 +0000 <Viking667> hm. Figures. I clearly missed that.
2021-05-25 07:58:01 +0000Viking667(viking@124.197.53.238) (Quit: *croak*)
2021-05-25 07:58:34 +0000Viking667(viking@124.197.53.238)
2021-05-25 08:12:21 +0000mc47(~yecinem@89.246.239.190)
2021-05-25 08:15:24 +0000dmwit_(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net)
2021-05-25 08:15:43 +0000dmwit(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net) (Ping timeout: 264 seconds)
2021-05-25 08:17:38 +0000allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 08:19:46 +0000joshproehl(~quassel@dtools-d10-tx-1.inf.daedalusdreams.com)
2021-05-25 08:20:26 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 252 seconds)
2021-05-25 08:24:19 +0000Viking667(viking@124.197.53.238) (*.net *.split)
2021-05-25 08:24:19 +0000wonko(~wjc@62.115.229.50) (*.net *.split)
2021-05-25 08:24:19 +0000qbt(~edun@user/edun) (*.net *.split)
2021-05-25 08:24:19 +0000td_(~td@muedsl-82-207-238-005.citykom.de) (*.net *.split)
2021-05-25 08:24:19 +0000eyenx(~eyenxeyen@eyenx.ch) (*.net *.split)
2021-05-25 08:24:19 +0000joshproehl_(~quassel@dtools-d10-tx-1.inf.daedalusdreams.com) (*.net *.split)
2021-05-25 08:24:43 +0000td_(~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 08:26:11 +0000allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 244 seconds)
2021-05-25 08:27:54 +0000wonko(~wjc@62.115.229.50)
2021-05-25 08:27:54 +0000qbt(~edun@user/edun)
2021-05-25 08:27:54 +0000eyenx(~eyenxeyen@eyenx.ch)
2021-05-25 08:29:28 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 08:37:21 +0000 <liskin> Solid: we can just use notify-send and fallback to xmessage
2021-05-25 08:37:40 +0000 <liskin> unfortunately notify-send doesn't seem to indicate whether it was able to send the notification or not :-)
2021-05-25 08:37:41 +0000 <liskin> :-(
2021-05-25 08:42:05 +0000 <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 08:42:42 +0000 <liskin> perhaps it would fail if I never had any dunst in the first place
2021-05-25 08:45:04 +0000 <Solid> doesn't report anything for me eitehr
2021-05-25 08:45:10 +0000 <Solid> and I don't use a notification daemon at all
2021-05-25 08:48:31 +0000 <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 08:56:11 +0000Bruners(lasseb@colargol.tihlde.org)
2021-05-25 08:59:14 +0000themainman(~themainma@user/themainman)
2021-05-25 09:04:22 +0000eyenx(~eyenxeyen@eyenx.ch) (Ping timeout: 264 seconds)
2021-05-25 09:05:40 +0000eyenx(~eyenxeyen@eyenx.ch)
2021-05-25 09:49:58 +0000 <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 09:50:33 +0000 <mc47> The type-level trickery intrigued me and I don't know where to read more about it
2021-05-25 09:51:38 +0000 <liskin> mc47: I don't have anything in particular that I'd recommend reading.
2021-05-25 09:52:04 +0000 <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 09:52:49 +0000 <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 09:53:31 +0000 <liskin> tldr is that Typeable lets you do dynamically typed values safely
2021-05-25 09:54:11 +0000 <liskin> the compiler generates instances of Typeable, which let you convert any type a into a Maybe specific type you want
2021-05-25 09:55:36 +0000 <mc47> that sounds really interesting, I'll check that out
2021-05-25 09:55:56 +0000 <mc47> Experiencing the evolution first-hand is really nice
2021-05-25 09:58:05 +0000 <liskin> it isn't the most cost effective way of learning stuff though
2021-05-25 09:58:32 +0000 <mc47> yes, but I think it gives a better insight
2021-05-25 10:01:45 +0000 <liskin> as long as you don't forget stuff :-)
2021-05-25 10:04:32 +0000 <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 10:04:51 +0000 <Solid> because we have Data.Typeable.TypeRep and Type.Reflection.TypeRep
2021-05-25 10:04:53 +0000 <Solid> both in base
2021-05-25 10:04:56 +0000 <Solid> this is a lot of fun :
2021-05-25 10:04:59 +0000 <Solid> :)
2021-05-25 10:05:52 +0000 <liskin> oh, Type.Reflection even has your `theType`
2021-05-25 10:05:57 +0000 <liskin> too bad it doesn't have cast :-(
2021-05-25 10:07:01 +0000 <liskin> (I know one can piece that together with eqTypeRep, but then it becomes ugly again)
2021-05-25 10:09:04 +0000 <Solid> it also can't really be put into a map as nicely (that I can see)
2021-05-25 10:09:12 +0000 <Solid> we'd have to existentially qualify over the whole map
2021-05-25 10:09:27 +0000 <Solid> I think Data.Typeable is definitely the better approach in our case
2021-05-25 10:10:34 +0000 <liskin> right
2021-05-25 10:23:51 +0000terrorjack(~terrorjac@ec2-54-95-39-30.ap-northeast-1.compute.amazonaws.com)
2021-05-25 11:05:37 +0000bsima1bsima
2021-05-25 11:14:24 +0000boxscape(~boxscape@user/boxscape)
2021-05-25 11:51:42 +0000Natch(~natch@c-e070e255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection)
2021-05-25 11:57:05 +0000Natch(~natch@c-e070e255.014-297-73746f25.bbcust.telenor.se)
2021-05-25 12:29:33 +0000a6a45081-2b83(~aditya@171.76.149.211)
2021-05-25 12:32:40 +0000f33f046c-a02e(~aditya@171.76.149.211)
2021-05-25 12:33:12 +0000a6a45081-2b83(~aditya@171.76.149.211) (Client Quit)
2021-05-25 12:47:36 +0000a6a45081-2b83(~aditya@27.58.166.71)
2021-05-25 12:47:36 +0000f33f046c-a02e(~aditya@171.76.149.211) (Read error: Connection reset by peer)
2021-05-25 12:51:46 +0000qbt(~edun@user/edun) (Ping timeout: 264 seconds)
2021-05-25 13:00:43 +0000a6a45081-2b83(~aditya@27.58.166.71) (Quit: Konversation terminated!)
2021-05-25 13:26:30 +0000dmwit_dmwit
2021-05-25 13:50:00 +0000qbt(~edun@user/edun)
2021-05-25 15:42:13 +0000qbt(~edun@user/edun) (Quit: WeeChat 3.1)
2021-05-25 15:50:21 +0000seschwar(~seschwar@user/seschwar)
2021-05-25 16:29:10 +0000boxscape(~boxscape@user/boxscape) (Quit: Connection closed)
2021-05-25 17:15:37 +0000boxscape(~boxscape@user/boxscape)
2021-05-25 17:18:18 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2021-05-25 17:23:06 +0000 <geekosaur> still nothing :(
2021-05-25 17:25:30 +0000 <liskin> at this point I'd consider popping into #libera or something and asking where in the queue they are
2021-05-25 17:34:08 +0000 <fizzie> On that note, FWIW, when I had our recommended pre-conversation with a staffer, they just set me as the relevant channel's founder and asked me to do the emails after-the-fact. So while it's not fully registered (re cloaks and whatever), at least we've got the right flags on the channel. So it sounds possible a staffer could help you get set up as well. (Though this was a community registration, not a
2021-05-25 17:34:14 +0000 <fizzie> project one.)
2021-05-25 17:35:08 +0000 <geekosaur> and the first thing I see on joining is someone else asking the same thing :)
2021-05-25 17:37:27 +0000 <geekosaur> main problems now being (1) I'm eating lunch (2) and having bad essential tremor today so I can barely type :(
2021-05-25 17:43:34 +0000 <geekosaur> oy
2021-05-25 17:48:04 +0000 <geekosaur> suspect that's the best answer we're going to get
2021-05-25 17:57:07 +0000allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 17:59:11 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 272 seconds)
2021-05-25 17:59:33 +0000allbery_bgeekosaur
2021-05-25 19:45:38 +0000 <geekosaur> did anyone test use of ppSort after reworking WorkspaceCompare? or if they did, perhaps we need migration documentation as it suggests the old form should work but it produces a type error now
2021-05-25 19:46:08 +0000 <geekosaur> that is, I can't say `ppSort = getSortByXineramaPhysicalRule`
2021-05-25 19:49:23 +0000 <liskin> geekosaur: are you referring to 756507e2b64786cca7e51263d59c51af1259c29d?
2021-05-25 19:49:29 +0000 <geekosaur> n/m, followed the types
2021-05-25 19:49:50 +0000 <geekosaur> the sort now can be by id or rectangle, I guess?
2021-05-25 19:56:15 +0000boxscape(~boxscape@user/boxscape) ()
2021-05-25 19:57:27 +0000 <geekosaur> well that was annoying.,. took 3 tries to figure out the right function to use
2021-05-25 19:57:53 +0000 <geekosaur> might do with better docs for ppSort indeed
2021-05-25 21:18:38 +0000ElKowar4(~ElKowar@srv-fin.xware-gmbh.de)
2021-05-25 21:19:53 +0000Solid_(~slot@2a01:4f8:c2c:d600::2)
2021-05-25 21:20:30 +0000liskin(~liskin@ackle.nomi.cz) (Ping timeout: 272 seconds)
2021-05-25 21:20:39 +0000jato(~jato@68.183.0.207) (Read error: Connection reset by peer)
2021-05-25 21:20:41 +0000piele(~piele@tbonesteak.creativeserver.net) (Read error: Connection reset by peer)
2021-05-25 21:20:47 +0000lambdabot(~lambdabot@haskell/bot/lambdabot) (Remote host closed the connection)
2021-05-25 21:20:50 +0000liskin(~liskin@ackle.nomi.cz)
2021-05-25 21:20:57 +0000seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-05-25 21:21:08 +0000ElKowar(~ElKowar@srv-fin.xware-gmbh.de) (Ping timeout: 272 seconds)
2021-05-25 21:21:21 +0000piele(~piele@tbonesteak.creativeserver.net)
2021-05-25 21:22:59 +0000lambdabot(~lambdabot@haskell/bot/lambdabot)
2021-05-25 21:23:01 +0000Solid(~slot@static.220.87.47.78.clients.your-server.de) (Ping timeout: 272 seconds)
2021-05-25 22:32:51 +0000mc47(~yecinem@89.246.239.190) (Remote host closed the connection)