search

saem / vscode-nim

Other
180 stars 23 forks source link

Goto definition/linting/etc broken even though choosenim is functional #102

Open creikey opened 1 year ago

creikey commented 1 year ago

My choosenim works fine with the other vscode extension (although that one is a lot slower). This is why I think this is separate from #97

creikey commented 1 year ago

I downloaded this project to try and fix this, and ran it myself, but the issue wasn't present. I think this has something to do with my nimble install compiler installing 1.6.6, my nim being 1.6.6, but the vscode extension having a previous version of nimsuggest ?

saem commented 1 year ago

This extension doesn't have nor installs any Nim tool chain. Unless something broke upstream it should just work, the extension simply find and uses whatever nimsuggest you have on your path.

I vaguely recall someone starting to change nimsuggest recently, perhaps that broke it. I'm not really following Nim anymore.

RSDuck commented 1 year ago

I can confirm that the extension to still works with nimsuggest build from devel source.