2025/07/23

Newest at the top

2025-07-23 23:14:15 +0200amadaluzia(~amadaluzi@user/amadaluzia) (Quit: ZNC 1.10.1 - https://znc.in)
2025-07-23 23:13:58 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-23 23:12:09 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-07-23 23:11:27 +0200Square3(~Square4@user/square) Square
2025-07-23 23:10:58 +0200jmcantrell_(~weechat@user/jmcantrell) (Ping timeout: 240 seconds)
2025-07-23 23:06:51 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 252 seconds)
2025-07-23 23:03:39 +0200 <geekosaur> jreicher: HLS points to lsp-mode which points to lsp-haskell and doesn't seem to mention eglot aside from tangentially
2025-07-23 23:03:28 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-07-23 23:02:32 +0200 <dolio> I doubt it will save much time if you care about someone who actually knows what's going on made sure the result makes sense.
2025-07-23 23:02:29 +0200 <geekosaur> oh, missed earlier response
2025-07-23 22:58:36 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-23 22:58:08 +0200 <glguy> dolio: maybe fixing this is what AI is for?
2025-07-23 22:57:46 +0200 <lambdabot> Unknown command, try @list
2025-07-23 22:57:46 +0200 <geekosaur> @Ricardo: hm, sorry, I wouldn't know from there. I actually moved to codium/vscode for programming so while I have some idea of how to configure emacs with LSP I don't know how well it works at this point
2025-07-23 22:57:12 +0200prdak(~Thunderbi@user/prdak) prdak
2025-07-23 22:56:54 +0200prdak(~Thunderbi@user/prdak) (Remote host closed the connection)
2025-07-23 22:55:21 +0200 <dolio> According to the issue tracking the proper fix, which is about a year old, the deprecated API is due to be actually removed soon. Maybe that's been delayed, though.
2025-07-23 22:52:33 +0200 <haskellbridge> <Ricardo> geekosaur: Thank you geekosaur ! I found the variable "lsp-haskell-formatting-provider" and, after changing it, emacs seems to be doing something different when saving the file. I notice the buffer scrolls while before it didn't, so I'm assuming the change took effect. Unfortunately, the formatter is still sorting imports. I changed it to "floskell" because floskell is supposed to not order imports by default.
2025-07-23 22:52:09 +0200trickard(~trickard@cpe-49-98-47-163.wireline.com.au) (Ping timeout: 260 seconds)
2025-07-23 22:51:55 +0200 <dolio> Also the situation doesn't seem great. :)
2025-07-23 22:51:51 +0200trickard__(~trickard@cpe-50-98-47-163.wireline.com.au)
2025-07-23 22:51:38 +0200 <dolio> Yeah, I mean, I know what I can do to build it. I was wondering what other people were actually doing.
2025-07-23 22:50:53 +0200 <tomsmeding> dolio: well then I guess the answer to "how do I build glirc" is "add a cabal.project with a source-repository-package that points to the hack-fix commit"
2025-07-23 22:50:42 +0200 <dolio> The fix is to rewrite the C bindings to a different API. There's an issue for that, but I don't see a lot of movement.
2025-07-23 22:50:38 +0200 <glguy> Maybe I'll fork hsopenssl and rip out all the stuff glirc doesn't need <_<
2025-07-23 22:50:13 +0200 <tomsmeding> software engineering :)
2025-07-23 22:50:03 +0200 <dolio> Turns off.
2025-07-23 22:49:57 +0200 <glguy> fixes or turns off?
2025-07-23 22:49:41 +0200 <dolio> There seems to be a patch that turns off the deprecation warnings, but a corresponding version hasn't been released to hackage yet.
2025-07-23 22:48:28 +0200 <tomsmeding> -Werror should be a thing in CI, possibly on one's dev machine, not in a released library
2025-07-23 22:48:06 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds)
2025-07-23 22:48:01 +0200 <dolio> Maybe it's because someone decided to -Werror.
2025-07-23 22:47:43 +0200 <dolio> All I know is that it doesn't build.
2025-07-23 22:47:41 +0200Lycurgus(~juan@user/Lycurgus) (Quit: irc.renjuan.org (juan@acm.org))
2025-07-23 22:47:19 +0200 <tomsmeding> apologies for the mis-mention
2025-07-23 22:47:12 +0200 <tomsmeding> dolio: ^
2025-07-23 22:47:02 +0200 <tomsmeding> degraafk: "deprecation errors"? Isn't the point of deprecation that it's still there but will be removed in the future?
2025-07-23 22:46:28 +0200dhil(~dhil@5.151.29.140) (Ping timeout: 240 seconds)
2025-07-23 22:43:12 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-07-23 22:40:56 +0200caubert(~caubert@user/caubert) caubert
2025-07-23 22:39:57 +0200ndudaev(~ndudaev@user/ndudaev) (Quit: WeeChat 3.8)
2025-07-23 22:35:40 +0200 <dolio> Maybe. It seems like my actual version is older than 3.5.
2025-07-23 22:35:16 +0200 <glguy> Perhaps the GCC Fedora is shipping is more aggressive about deprecations that the clang macOS comes iwth
2025-07-23 22:33:53 +0200ndudaev(~ndudaev@user/ndudaev) ndudaev
2025-07-23 22:33:51 +0200jmcantrell_(~weechat@user/jmcantrell) jmcantrell
2025-07-23 22:31:58 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-07-23 22:30:44 +0200 <glguy> I have openssl 3.5.1
2025-07-23 22:30:25 +0200 <glguy> dolio: I build on Apple Silicon mac and I have to do https://paste.tomsmeding.com/lC0pl5t6 which doesn't have that I guess
2025-07-23 22:30:21 +0200 <dolio> Has for a while, actually.
2025-07-23 22:30:07 +0200 <dolio> Fedora 42. It has a new enough openssl to trigger deprecation errors for the C bindings in HsOpenSSL.