Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

> We really also should have pre-compiled ARM versions for both Linux and Mac. Agree. Or just provide the C sources pre-cross-compiled for these targets.

Dark Theme Problem in Nim Manual

Known issue =>

Dark Theme Problem in Nim Manual

[Nim Experimental Features](https://nim-lang.github.io/Nim/manual_experimental.html) works fine, too.

Dark Theme Problem in Nim Manual

It seems to happen at the newest version, where the background is all-white and the words are all-black, while the [1.6.0 documentation](https://nim-lang.org/1.6.0/manual.html) is colored correctly.

Dark Theme Problem in Nim Manual

It's not just you. In brave and firefox I get an error like > Uncaught ReferenceError: setTheme is not defined at HTMLSelectElement.onchange Something odd? Open the developer console. See an error that isn't your fault? Report it.

Dark Theme Problem in Nim Manual

I found that the dark theme in the [Nim Manual](https://nim-lang.org/docs/manual.html) doesn't work. Is this a bug or just something wrong on my end?

Nim Autome / Win32 API

anyone here work with the win32 api or the autome() package recently? I'm working on basic moving and clicking and seem to be failing on the `click()` proc nim c -r main.nim Run import autome mouse .move(25,840)

Show Nim: JWTea, Crunchy and Depot. New repos you may find useful.

I am sorry. I didn't see any work by you for a while. Please forget it.

Show Nim: JWTea, Crunchy and Depot. New repos you may find useful.

What does "away" from GitHub mean or where are you seeing that?

Is ORC considered production-ready? What is the consensus on its use?

Thanks! To be clear I don’t think ARC should be officially supported. Rather as you mention avoiding cycles is more efficient. Though I do plan to try and use Chronos with ARC on embedded someday. That’s a niche case though and requires devs to design carefully. Hmmm, it possibly could be usefu

CBOR?

I do use MsgPack. Though CBOR while a “clone” of MsgPack also adds more ability for extensions via custom tags. There’s standard tags for things like JWT, GPS locations, etc. It also has a bunch of standardizations including RPC that’s widely used in IoT. The main downside is that implementing

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

Also choosemim on ARM Macs installs an x86-64 build of the compiler. Rosetta is fast but it still slows down the compilation. I use ASDF as it also handles nodejs, elixir, etc. However it doesn’t work on windows AFAICT. We really also should have pre-compiled ARM versions for both Linux and Mac

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

Oh, I wasn't aware. I thought it only did packages. Haven't looked into it, but I guess this could be a better solution then.

Trouble Porting to FreeBSD

My observation related to the FreeBSD port of Nim. Several months ago, I need to play with the development version of Nim. First I tried to install it in FreeBSD way, by upgrading the existing port. It didn't build. So I built Nim manually, with the standard `./build_all.sh` command. It worked

Nim version 2.0.0 is here

Congratulations for everyone!

Nim version 2.0.0 is here

Congratulations on the release and a big thank you to everyone who contributed to making Nim better!

Trouble Porting to FreeBSD

@nealie Thank you for working on this, much appreciated.

Nim version 2.0.0 is here

Thank you all Nim-team!

Trouble Porting to FreeBSD

> This probably means I have some path set wrongly somewhere in the > configuration, or I haven't managed to modify some path search to use the > required directory structure. Most probably, yes.

Trouble Porting to FreeBSD

Alas it's not that simple as to make the port I have to conform the the porting rules, that nim breaks unfortunately. This hasn't been a problem for some time as the port has been in good shape and has merely needed updating, but with the move to 2.0.0, things seem to have changed a bit more. I

Trouble Porting to FreeBSD

Thank you for your contribution to the discussion.

Nim version 2.0.0 is here

Normally this is antivirus-related stuff

Trouble Porting to FreeBSD

I guess helloSystem?

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

> Choosenim is the best way to have the latest Nim version around while still > being able to jump to devel versions or a local copy. Is it though? Atlas can do the same already.

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

Let's instead start maintaining it.. Choosenim is the best way to have the latest Nim version around while still being able to jump to devel versions or a local copy.

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

Maybe choosenim should be removed from since it's unmaintained for so long.

Trouble Porting to FreeBSD

I use Nim on a FreeBSD variant all the time and things just work. However, I simply set my PATH to $nim/bin and don't deal with the /usr/bin stuff.

Trouble Porting to FreeBSD

I'm working on the FreeBSD port of nim. Everything build OK and I've managed to get it installed, but the installed compiler seems to have problems. I'm having trouble as modules in the standard library that import other standard library modules, but without a std/ prefix don't seem to work (the

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

I am but I don't use choosenim. You can always build from source, easily. Follow these steps: git clone https://github.com/nim-lang/csources_v2 cd csources_v2 make -j 8 cd .. git clone https://github.com/nim-lang/nim mv csources_v2/bin/nim nim/bin cd nim b

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

Are you on apple silicon? I found a bug report describing the issue here so I think its been around for a bit: Is there any way to get old nim versions precompiled for mac (specifically 1.6.14)? Unfortunately brew doesn't let you download old versi

newSeq() named inconsistently?

there once was a point where it was easier to have momentum on stuff like this, in spite of w/e significance it has and whatever degree of relation it has to the "bigger picture" of the language as a whole, primarily because there were fewer affected parties using the language in general. this i

Any way to produce Arm64 binaries for MacOS from choosenim versions of nim?

For me `--cpu:arm64` does make a difference. I used the `file` command to confirm.