<< 03-08-2026 >>

00:11:52*Mister_Magister quit (Quit: bye)
00:13:48*Mister_Magister joined #nim
00:31:59*ftajhii joined #nim
03:35:44*rockcavera quit (Remote host closed the connection)
04:07:40*hygo quit (Read error: Connection reset by peer)
04:13:12*hygo joined #nim
04:55:12*Pixi` joined #nim
04:58:17*Pixi quit (Ping timeout: 253 seconds)
04:59:50*Pixi joined #nim
05:00:28*Pixi` quit (Ping timeout: 264 seconds)
05:59:32*th3r00t quit (Quit: ZNC 1.10.2 - https://znc.in)
06:03:12*th3r00t joined #nim
06:11:17*th3r00t quit (Quit: ZNC 1.10.2 - https://znc.in)
06:16:49*th3r00t joined #nim
06:21:35*ftajhii quit (Ping timeout: 257 seconds)
07:46:17*SchweinDeBurg quit (Remote host closed the connection)
07:46:55*SchweinDeBurg joined #nim
08:36:42*beholders_eye joined #nim
11:48:40*Skippy8 joined #nim
12:00:42*xet7 joined #nim
12:05:57*Skippy8 quit (Ping timeout: 260 seconds)
12:08:39*Skippy8 joined #nim
12:37:19*SchweinDeBurg quit (Remote host closed the connection)
12:37:34*SchweinDeBurg joined #nim
13:20:12FromDiscord<pmunch> What's up with Nimble suddenly installing Nim over and over again?
13:21:02FromDiscord<pmunch> Tried to use the `--useSystemNim` switch and it said it couldn't find it even though I have multiple versions installed through choosenim and the currently selected version in my path..
13:51:36FromDiscord<nasuray> In reply to @pmunch "Tried to use the": which version of `nimble` are you on? this should have been fixed.
13:52:40FromDiscord<nasuray> In reply to @pmunch "What's up with Nimble": without `--useSystemNim` if nim is in a `nimble.lock` and the versions don't match then it downloads a release (or source -> compile)
14:00:06*nariyel quit (Changing host)
14:00:06*nariyel joined #nim
14:21:13*tokyovigilante_ joined #nim
14:21:53*tokyovigilante quit (Read error: Connection reset by peer)
14:21:53*tokyovigilante_ is now known as tokyovigilante
14:31:41FromDiscord<pmunch> `nimble v0.22.2 compiled at 2026-04-24 03:46:34`
14:32:28FromDiscord<pmunch> I've never created a nimble.lock file, so if one exists Nimble created it itself
14:34:58FromDiscord<zumi.dxy> I was wondering that I somehow did something wrong there when it said "installing Nim 2.something" even with that switch↵I did use the nimble abspath though so like idk
14:59:02FromDiscord<nasuray> In reply to @pmunch "`nimble v0.22.2 compiled at": I think updating to 0.24.1 should resolve this (at the very least --useSystemNim should work)
15:10:58FromDiscord<pmunch> Nimble is installed with Nimble, so the 2.2.10 release ships with this broken Nimble
15:12:01FromDiscord<pmunch> It really feels like every new release ships a Nimble that's broken in a slightly different way. And the fix is always "just update to this version", but by the time the next Nim version is released Nimble has been broken in a different way
15:12:33FromDiscord<pmunch> So when using Nimble you then have to keep the Nim install from there and sideload Nimble to get a working version, which is really annoying
15:28:43*Skippy8 quit (Ping timeout: 244 seconds)
15:37:48FromDiscord<nasuray> In reply to @pmunch "So when using Nimble": Yes I agree...I'm desperately trying to remain optimistic that the increased instability now leads to a more stable nimble in the future...perhaps the bundles installed by choosenim/grabnim should package the most up to date nimble rather than the latest at the time of that Nim release.
15:53:47*Skippy8 joined #nim
16:00:55*Skippy8 quit (Ping timeout: 264 seconds)
16:27:36*Skippy8 joined #nim
16:31:42*Skippy8 quit (Ping timeout: 242 seconds)
16:35:53*Skippy8 joined #nim
16:50:22*Skippy8 quit (Ping timeout: 268 seconds)
16:59:54*beholders_eye quit (Ping timeout: 245 seconds)
17:01:48*Skippy8 joined #nim
17:06:06*Skippy8 quit (Ping timeout: 252 seconds)