You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some projects don't / can't use Nimble. It'd be great to have support for projects using Atlas (or the older Nimbus build system). My previous tests with nimlangserver resulted in a bunch of nimble errors occuring.
Idealling this could be done by modifying to check for a nim.cfg which specifies a --noNimblePath switch. I'm not sure if Nim's dump config will specifies that or not.
Alternatively, a nimlangserver config to manually disable using Nimble would work as well.
The text was updated successfully, but these errors were encountered:
I also wonder if it's possible to replace the getProjectFileAutoGuess with running nim to dump the path configs?
Would running nim dump --verbosity:0 --dump.format:json dump.json | jq give all the path info necessary? It seems like it's just trying to find paths, but I haven't dug into getProjectFileAutoGuess to see exactly what it's getting.
nimlangserver binaries don't need to be compiled
anymore for common platforms .
after each commit , automatically compiled
fresh new binaries are available at https://github.com/nim-lang/langserver/releases
nimlangserver binaries don't need to be compiled anymore for common platforms . after each commit , automatically compiled fresh new binaries are available at https://github.com/nim-lang/langserver/releases
Some projects don't / can't use Nimble. It'd be great to have support for projects using Atlas (or the older Nimbus build system). My previous tests with nimlangserver resulted in a bunch of nimble errors occuring.
Idealling this could be done by modifying to check for a
nim.cfg
which specifies a--noNimblePath
switch. I'm not sure if Nim's dump config will specifies that or not.Alternatively, a nimlangserver config to manually disable using Nimble would work as well.
The text was updated successfully, but these errors were encountered: