2022/07/07

2022-07-07 00:31:18 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:753b:477d:ff71:8b54) (Ping timeout: 276 seconds)
2022-07-07 00:31:30 +0200sogens(~sogens@gateway/vpn/pia/sogens) (Ping timeout: 240 seconds)
2022-07-07 00:32:50 +0200 <craige[m]> <geekosaur> "not like someone's pointing a..." <- NixOS has picked it up 😃
2022-07-07 00:33:41 +0200sogens(~sogens@211.30.26.217)
2022-07-07 00:35:10 +0200td_(~td@94.134.91.239) (Ping timeout: 244 seconds)
2022-07-07 00:37:36 +0200td_(~td@94.134.91.239)
2022-07-07 00:42:58 +0200 <liskin> and opensuse, and most of the bsds
2022-07-07 00:44:59 +0200 <liskin> would probably be fair to build test some of the BSDs in CI
2022-07-07 00:45:22 +0200 <liskin> but that wouldn't catch any bugs like if we ever decide to touch SIGCHLD handling or something :-/
2022-07-07 00:45:49 +0200 <liskin> anyway, low prio, need to sleep, only 6 hours remaining until I need to get up and cycle 40k to London :-)
2022-07-07 00:46:17 +0200 <geekosaur> mm, was wondering, should we put an impossible constraint on impl(ghc >= 9.0 && < 9.4)?
2022-07-07 00:46:27 +0200 <geekosaur> due to the join point bug?
2022-07-07 00:46:53 +0200 <liskin> (and possibly 60k if the train company decides to keep the pre-covid rule of not taking bikes during peak times)
2022-07-07 00:47:48 +0200 <liskin> geekosaur: probably not as that would exclude point releases as well
2022-07-07 00:48:15 +0200 <liskin> maybe an #if #warning might be helpful though
2022-07-07 00:48:44 +0200 <liskin> but then… why isn't like everybody hitting the bug? do most people run ghc 8.* ?
2022-07-07 00:49:05 +0200 <liskin> (I do, but I'm on Debian, which has been late even when it had people maintaining this stuff… :-))
2022-07-07 00:49:09 +0200 <geekosaur> 8.10.7 is still the most used version, yes. and it only shows with specific kinds of join points
2022-07-07 00:49:28 +0200 <geekosaur> specifically how we do this long running FFI inside a forever
2022-07-07 00:50:00 +0200 <liskin> can we perhaps write a version of forever that doesn't trigger the bug?
2022-07-07 00:50:29 +0200 <geekosaur> which confuses codegen into thinking it's unreachable in some fashion, so it drops the keepAlive# and the next gc removes the allocaEvent and the heap subsequently gets smashed
2022-07-07 00:50:47 +0200 <geekosaur> I was thinking just recursively reinvoke the function
2022-07-07 00:50:59 +0200 <geekosaur> instead of ending it with a forever
2022-07-07 00:52:30 +0200 <liskin> or that, whatever works, is obviously correct and is easy to revert
2022-07-07 00:53:41 +0200 <liskin> anyway, afk for real
2022-07-07 00:55:05 +0200kaskal-(~kaskal@089144220061.atnat0029.highway.webapn.at)
2022-07-07 00:57:13 +0200 <kaskal-> Hi! I wanted to share my xmonad configuraiton, it has keybindings like emacs to enter modes (GUI-C GUI-S) enters screenshot mode, or (GUI-C GUI-M) enters mpd controler mode https://github.com/alejandrogallo/xmonad-config
2022-07-07 00:57:27 +0200 <kaskal-> Maybe it is useful for someone
2022-07-07 01:06:45 +0200 <geekosaur> we really need to bring back the config gallery at some point
2022-07-07 01:06:51 +0200 <geekosaur> the current one's way bitrotted
2022-07-07 01:35:28 +0200 <geekosaur> not as easy as I had hoped, sadly. showoffy code means pain later…
2022-07-07 01:57:17 +0200redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2022-07-07 01:58:05 +0200redgloboli(~redglobol@user/redgloboli)
2022-07-07 02:06:00 +0200redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2022-07-07 02:06:50 +0200redgloboli(~redglobol@user/redgloboli)
2022-07-07 02:21:36 +0200werneta(~werneta@137.78.30.207) (Ping timeout: 244 seconds)
2022-07-07 02:32:58 +0200sogens(~sogens@211.30.26.217) (Ping timeout: 244 seconds)
2022-07-07 02:35:15 +0200sogens(~sogens@211.30.26.217)
2022-07-07 03:04:30 +0200sogens(~sogens@211.30.26.217) (Ping timeout: 240 seconds)
2022-07-07 03:06:44 +0200sogens(~sogens@gateway/vpn/pia/sogens)
2022-07-07 03:25:33 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-07-07 04:03:54 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 244 seconds)
2022-07-07 04:23:00 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-07-07 04:33:57 +0200td_(~td@94.134.91.239) (Ping timeout: 256 seconds)
2022-07-07 04:35:38 +0200td_(~td@muedsl-82-207-238-170.citykom.de)
2022-07-07 06:19:16 +0200sogens(~sogens@gateway/vpn/pia/sogens) (Ping timeout: 244 seconds)
2022-07-07 06:21:31 +0200joshproehl(~quassel@user/joshproehl) (Remote host closed the connection)
2022-07-07 06:21:33 +0200sogens(~sogens@211.30.26.217)
2022-07-07 06:22:25 +0200joshproehl(~quassel@user/joshproehl)
2022-07-07 06:30:35 +0200darkstardevx(~darkstard@50.53.212.60)
2022-07-07 07:01:44 +0200nev_yn(~nyven@c-68-43-234-118.hsd1.mi.comcast.net)
2022-07-07 08:18:13 +0200valarMorghulis[m(~lladeebll@2001:470:69fc:105::2:72)
2022-07-07 08:22:44 +0200sogens(~sogens@211.30.26.217) (Remote host closed the connection)
2022-07-07 08:28:47 +0200sogens(~sogens@gateway/vpn/pia/sogens)
2022-07-07 08:39:24 +0200samhh(7569f027cf@2604:bf00:561:2000::e4) (Read error: Connection reset by peer)
2022-07-07 08:39:24 +0200alethkit(23bd17ddc6@2604:bf00:561:2000::3ce) (Read error: Connection reset by peer)
2022-07-07 08:39:26 +0200raghavgururajan(ea769b8000@user/raghavgururajan) (Read error: Connection reset by peer)
2022-07-07 08:39:37 +0200samhh(7569f027cf@2604:bf00:561:2000::e4)
2022-07-07 08:40:07 +0200raghavgururajan(ea769b8000@user/raghavgururajan)
2022-07-07 08:40:08 +0200alethkit(23bd17ddc6@2604:bf00:561:2000::3ce)
2022-07-07 08:40:55 +0200 <valarMorghulis[m> I was trying to implement top bar in xmonad to show active window instead of the boarder. If I user `noFillsDeco` the problem is that it's not smart even if there is just one window it shows the top bar, therefore I got a code snippet for smart top bar from reddit and I'm using it. It works well but when I try to... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/ca97236c24e423bbafe125e2d0017755dcbb…)
2022-07-07 08:41:33 +0200valarMorghulis[muploaded an image: (819KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/rqTBAUvcrKbYqaxLrmafGGoy/2022-07-07_1… >
2022-07-07 08:41:35 +0200valarMorghulis[muploaded an image: (824KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/DoXguIgEFuENaSAxtiGwwCHS/2022-07-07_1… >
2022-07-07 08:42:59 +0200 <valarMorghulis[m> The first screenshot is with smart bar and thats the issue I'm talking about, and the second screenshot is with `noFrillsdeco` and thats the desired output
2022-07-07 09:02:54 +0200cfricke(~cfricke@user/cfricke)
2022-07-07 09:29:22 +0200chomwitt(~chomwitt@2a02:587:dc0d:4a00:ceae:439a:35c2:d6cc)
2022-07-07 09:53:59 +0200sogens(~sogens@gateway/vpn/pia/sogens) (Remote host closed the connection)
2022-07-07 09:55:38 +0200mc47(~mc47@xmonad/TheMC47)
2022-07-07 10:15:37 +0200benin0(~benin@183.82.27.194)
2022-07-07 10:51:50 +0200benin0(~benin@183.82.27.194) (Ping timeout: 240 seconds)
2022-07-07 11:08:59 +0200 <liskin> geekosaur: perhaps there's a way to make the gallery self-maintaining…
2022-07-07 11:10:08 +0200 <liskin> what comes to mind is some kind of modern shit like yaml with links to people's dotfiles repos with some metadata like description and where's the screenshot located, and a github action that updates it at regular intervals
2022-07-07 11:10:38 +0200 <liskin> it'd be deepening our dependency on github though
2022-07-07 11:10:51 +0200 <liskin> quite far down that road anyway, I guess.
2022-07-07 11:29:47 +0200noex(~null@user/noex) (Ping timeout: 244 seconds)
2022-07-07 11:31:42 +0200noex(~null@user/noex)
2022-07-07 12:41:21 +0200alternateved(~alternate@staticline-31-183-144-54.toya.net.pl)
2022-07-07 13:06:04 +0200 <kaskal-> We could also do a repo with a makefile per configuration that fetches the stuff from a user-provided repo every week and commits everything altogether in this single repo. That way we are not dependent if the original user removes the original repo and everything would be self-contained in this single repo. Musts are a Makefile with couple of
2022-07-07 13:06:05 +0200 <kaskal-> variables and a README file. And of course the license of the configuration
2022-07-07 13:07:20 +0200 <kaskal-> and if the service provides like easy enough CI or free, then you can do the building everytime it gets updated, like in mine
2022-07-07 13:11:32 +0200twiclo1(~twiclo@vpn.utahbroadband.com) (Quit: WeeChat 3.5)
2022-07-07 14:11:33 +0200 <liskin> Good point that we don't really need to depend on that much GH-Action-y stuff
2022-07-07 14:26:07 +0200scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Quit: leaving)
2022-07-07 14:26:21 +0200scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2022-07-07 15:15:49 +0200 <kaskal-> if it's there, we can use it, but otherwise, nowadays having a simple shell.nix file like in https://github.com/alejandrogallo/xmonad-config/blob/master/shell.nix is enough to setup most xmonad relevant workflows, as long as the CI supports nix
2022-07-07 15:36:41 +0200 <liskin> Every CI supports Nix. In our case, the people would be the bigger problem :-D
2022-07-07 15:38:08 +0200 <liskin> (Not being a NixOS user myself and not having a Haskell day job means I haven't learnt Nix yet.)
2022-07-07 15:48:52 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at)
2022-07-07 15:50:37 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at) (Client Quit)
2022-07-07 16:05:38 +0200 <dminuoso> Be glad. I want my time learning nix/nixos back!
2022-07-07 16:14:01 +0200 <kaskal-> dminuoso indeed... but it has already the place allocated in my brain and for people like liskin if you give them the shell.nix file and a makefile and you tell them just do nix-shell and you have a shell with all the environment in place, that's good enough for practical purposes. But yes, beware, nixos = pain at the beginning for sure
2022-07-07 16:15:31 +0200alternateved(~alternate@staticline-31-183-144-54.toya.net.pl) (Remote host closed the connection)
2022-07-07 16:20:15 +0200 <liskin> dminuoso: can't tell if you're joking or not :-)
2022-07-07 16:21:04 +0200 <liskin> kaskal-: if you tell me to just do nix-shell I won't do it :-D
2022-07-07 16:22:19 +0200 <liskin> (although maybe I would, in a VM, to see what it does, and then maybe later I'd be comfortable running that on my main machine too)
2022-07-07 16:24:04 +0200 <geekosaur> the times I've had nox installed I kept it sandboxed. the flip side of its being hermetically sealed against the native OS sneaking in is you can sandbox it just by not running its environment setup
2022-07-07 16:24:37 +0200 <geekosaur> alias nix='. /home/allbery/.nix-profile/etc/profile.d/nix.sh; psys "nix${_BSA_PSYS++$_BSA_PSYS}"'
2022-07-07 16:25:12 +0200 <liskin> oh does it work without the daemon and stuff?
2022-07-07 16:25:13 +0200 <geekosaur> so I know where it's active as well (psys adds a mark to the prompt)
2022-07-07 16:25:35 +0200 <geekosaur> nixos may have a daemon, I haven't noticed one otherwise
2022-07-07 16:25:58 +0200 <geekosaur> can't check now, haven't had a need to install nix on this laptop
2022-07-07 16:33:16 +0200 <kaskal-> liskin I get it ;) However such a shell file can be a trivial one (as is in my case), and then you have to kind of trust the nix people to have kosher packages, which it seems to be the case
2022-07-07 16:33:33 +0200 <geekosaur> I would think I'd have noticed a daemon if it used any significant amount of memory, back when I was stuck on the 2gb netbook
2022-07-07 16:44:32 +0200 <liskin> kaskal-: yeah it's more about this weird obsession of mine of trying to understand how stuff works before using it
2022-07-07 16:44:54 +0200 <liskin> there is not any sane/reasonable argument to be made :-)
2022-07-07 16:45:25 +0200 <geekosaur> dunno, that sounds sane to me
2022-07-07 16:45:40 +0200 <geekosaur> just more and more impossible these days 😕
2022-07-07 16:50:50 +0200 <liskin> well that's kind of the definition of insane isn't it?
2022-07-07 16:51:16 +0200 <liskin> impossible in relation to the shared reality of society at the time
2022-07-07 17:21:30 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.5)
2022-07-07 17:22:21 +0200 <dminuoso> liskin: Neither do I. I think Nix/NixOS would be completely great, if it wasnt for the extremely steep learning curve or its piss poor UX
2022-07-07 17:37:18 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at)
2022-07-07 17:41:50 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-07-07 18:00:17 +0200theliver[m](~theliverm@2001:470:69fc:105::2:25e4) (Quit: You have been kicked for being idle)
2022-07-07 20:50:02 +0200dschrempf(~dominik@mobiledyn-62-240-134-33.mrsn.at) (Quit: WeeChat 3.5)
2022-07-07 22:09:40 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net)