Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→
Page 1 2 3 4 5 6 7 8 9 10 .. 1842
184,149 events total
2021-05-24 21:02:46 × triskai quits (~relikt@216-164-151-15.s8205.c3-0.atw-cbr1.atw.pa.cable.rcncustomer.com) (Read error: Connection reset by peer)
2021-05-24 21:31:00 geekosaur joins (~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-24 21:31:27 × allbery_b quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 264 seconds)
2021-05-24 21:58:09 × seschwar quits (~seschwar@user/seschwar) (Quit: :wq)
2021-05-24 22:32:21 × themc47 quits (~yecinem@89.246.239.190) (Remote host closed the connection)
2021-05-24 22:45:43 × qbt quits (~edun@user/edun) (Quit: WeeChat 3.1)
2021-05-24 22:45:52 × themainman quits (~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-24 22:46:10 themainman joins (~themainma@user/themainman)
2021-05-25 00:25:40 wz1000_ joins (~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 00:25:53 × wz1000 quits (~zubin@static.11.113.47.78.clients.your-server.de) (Ping timeout: 264 seconds)
2021-05-25 00:28:01 × fizzie quits (fis@selene.zem.fi) (Ping timeout: 264 seconds)
2021-05-25 00:29:08 fizzie joins (fis@selene.zem.fi)
2021-05-25 01:18:21 × themainman quits (~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-25 01:43:14 Viking667 joins (viking@124.197.53.238)
2021-05-25 01:43:38 <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 × td__ quits (~td@94.134.91.149) (Ping timeout: 264 seconds)
2021-05-25 02:40:03 td_ joins (~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 03:04:58 × boxscape quits (~boxscape@user/boxscape) (Ping timeout: 264 seconds)
2021-05-25 04:39:17 × geekosaur quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 272 seconds)
2021-05-25 04:42:19 geekosaur joins (~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 05:03:11 <dmwit> Viking667: Sounds right.
2021-05-25 05:03:44 <dmwit> vrs: That's against freenode rules now. Censorship, man
2021-05-25 05:16:58 × abhixec quits (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 264 seconds)
2021-05-25 05:36:45 <Solid> Once we have OP here we should just set +f ##xmonad-has-moved-to-libera or something
2021-05-25 05:37:05 <Solid> *set that on freenode
2021-05-25 06:02:16 qbt joins (~edun@user/edun)
2021-05-25 06:09:18 × qbt quits (~edun@user/edun) (Read error: Connection reset by peer)
2021-05-25 06:11:04 qbt joins (~edun@user/edun)
2021-05-25 06:15:21 wonko joins (~wjc@62.115.229.50)
2021-05-25 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
2021-05-25 07:17:53 wz1000_ is now known as wz1000
2021-05-25 07:18:05 <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 × wz1000 quits (~zubin@static.11.113.47.78.clients.your-server.de) (Quit: WeeChat 2.8)
2021-05-25 07:18:21 wz1000 joins (~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 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?
2021-05-25 07:18:51 <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 <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 <Solid> Viking667: that _is_ recompiling :)
2021-05-25 07:20:36 <vrs> I'd kind of like a version of xmessage that displays unicode properly
2021-05-25 07:21:53 <Viking667> Solid: so what's "xmonad --restart" then?
2021-05-25 07:22:09 <Viking667> Because that's what I use, and is what is inside my xmonad.hs
2021-05-25 07:22:25 × wz1000 quits (~zubin@static.11.113.47.78.clients.your-server.de) (Client Quit)
2021-05-25 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
2021-05-25 07:27:13 wz1000 joins (~zubin@2a01:4f8:1c0c:40d9::1)
2021-05-25 07:28:06 × wz1000 quits (~zubin@2a01:4f8:1c0c:40d9::1) (Client Quit)
2021-05-25 07:28:15 wz1000 joins (~zubin@static.11.113.47.78.clients.your-server.de)
2021-05-25 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.
2021-05-25 07:29:48 <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 <Solid> what I'm saying is that you define xmonad's main function inside your xmonad.hs
2021-05-25 07:38:14 <Solid> It's not a config file that is just read and then incorporated into the program
2021-05-25 07:38:19 <Solid> it is the starting point of the program
2021-05-25 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
2021-05-25 07:39:45 <Solid> If you have an .xsession.log or similar you'll probably find compilation messages there
2021-05-25 07:43:01 <Viking667> hm. Figures. I clearly missed that.
2021-05-25 07:58:01 × Viking667 quits (viking@124.197.53.238) (Quit: *croak*)
2021-05-25 07:58:34 Viking667 joins (viking@124.197.53.238)
2021-05-25 08:12:21 mc47 joins (~yecinem@89.246.239.190)
2021-05-25 08:15:24 dmwit_ joins (~dmwit@pool-173-66-86-32.washdc.fios.verizon.net)
2021-05-25 08:15:43 × dmwit quits (~dmwit@pool-173-66-86-32.washdc.fios.verizon.net) (Ping timeout: 264 seconds)
2021-05-25 08:17:38 allbery_b joins (~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 08:19:46 joshproehl joins (~quassel@dtools-d10-tx-1.inf.daedalusdreams.com)
2021-05-25 08:20:26 × geekosaur quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 252 seconds)
2021-05-25 08:24:19 × Viking667 quits (viking@124.197.53.238) (*.net *.split)
2021-05-25 08:24:19 × wonko quits (~wjc@62.115.229.50) (*.net *.split)
2021-05-25 08:24:19 × qbt quits (~edun@user/edun) (*.net *.split)
2021-05-25 08:24:19 × td_ quits (~td@muedsl-82-207-238-005.citykom.de) (*.net *.split)
2021-05-25 08:24:19 × eyenx quits (~eyenxeyen@eyenx.ch) (*.net *.split)
2021-05-25 08:24:19 × joshproehl_ quits (~quassel@dtools-d10-tx-1.inf.daedalusdreams.com) (*.net *.split)
2021-05-25 08:24:43 td_ joins (~td@muedsl-82-207-238-005.citykom.de)
2021-05-25 08:26:11 × allbery_b quits (~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 244 seconds)
2021-05-25 08:27:54 wonko joins (~wjc@62.115.229.50)
2021-05-25 08:27:54 qbt joins (~edun@user/edun)
2021-05-25 08:27:54 eyenx joins (~eyenxeyen@eyenx.ch)
2021-05-25 08:29:28 geekosaur joins (~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-25 08:37:21 <liskin> Solid: we can just use notify-send and fallback to xmessage
2021-05-25 08:37:40 <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 <liskin> :-(
2021-05-25 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 :-/
2021-05-25 08:42:42 <liskin> perhaps it would fail if I never had any dunst in the first place
2021-05-25 08:45:04 <Solid> doesn't report anything for me eitehr
2021-05-25 08:45:10 <Solid> and I don't use a notification daemon at all
2021-05-25 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
2021-05-25 08:56:11 Bruners joins (lasseb@colargol.tihlde.org)
2021-05-25 08:59:14 themainman joins (~themainma@user/themainman)
2021-05-25 09:04:22 × eyenx quits (~eyenxeyen@eyenx.ch) (Ping timeout: 264 seconds)
2021-05-25 09:05:40 eyenx joins (~eyenxeyen@eyenx.ch)
2021-05-25 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
2021-05-25 09:50:33 <mc47> The type-level trickery intrigued me and I don't know where to read more about it
2021-05-25 09:51:38 <liskin> mc47: I don't have anything in particular that I'd recommend reading.
2021-05-25 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 :-/
2021-05-25 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
2021-05-25 09:53:31 <liskin> tldr is that Typeable lets you do dynamically typed values safely
2021-05-25 09:54:11 <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 <mc47> that sounds really interesting, I'll check that out
2021-05-25 09:55:56 <mc47> Experiencing the evolution first-hand is really nice
2021-05-25 09:58:05 <liskin> it isn't the most cost effective way of learning stuff though
2021-05-25 09:58:32 <mc47> yes, but I think it gives a better insight
2021-05-25 10:01:45 <liskin> as long as you don't forget stuff :-)
2021-05-25 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)
2021-05-25 10:04:51 <Solid> because we have Data.Typeable.TypeRep and Type.Reflection.TypeRep
←Prev  Next→
Page 1 2 3 4 5 6 7 8 9 10 .. 1842

All times are in UTC.