MordechaiHadad

@kristijanhusak @mosheavni hello yeah i recently fixed it(I hope for everyone) with commit f1585abada425874546c0145224f009d17704d3a I will reopen this issue until it is fully resolved

@mrxiaozhuox currently M1 is not supported I am actually surprised you got bob running in the first place... there's also a #22 which I am meaning to resolve, but since...

> I get the same error with amd CPU Okay now this is weird can you provide what OS you are using?(Unless you are using MacOS I don't really know...

This will be a bit harder to debug as I don't own a Mac Machine, so i will need someone to actively test when I open the related PR.

@mrxiaozhuox that is good thank you! I will try looking at the code base tomorrow and just see what line of code might have triggered this weird error.

Would be great if u can test the PR CI builds and give me feedback @mrxiaozhuox

Hello! thanks for opening the issue. I too have no idea how to get previous nightly builds, I was suggested before being able to build neovim from a specific commit...

Great timing lol i was just looking into this!

Hello so after looking up online regarding ARM compilation, this will sadly have to wait sometime... Until either GitHub actions or cross-rs/cross have M1 support I'm going to wait. I...

> > > there are no dynamic libs on NixOS so dynamically linked lsps wont run > > ``` > /home/jk/.local/share/nvim/lspmanager/rust_analyzer/./rust-analyzer` failed: ENOENT: no such file o > r directory...