Home liberachat/#xmonad: Logs Calendar

Logs on 2021-05-25 (liberachat/#xmonad)

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

All times are in UTC on 2021-05-25.