Open
Conversation
When running `nimble vsix` I was getting this error: > vscode-nim/src/tools/elrpc.nim(6, 18) Error: cannot open file: nimsuggest/sexp This is because nimsuggest is not in the nim installation’s lib directory. These changes explicitly add the nim installation’s root directory to the search path so that nimsuggest can be found when compiling.
I was seeing errors like this in the Nim Language Server output: > DBG Failed to parse the configuration. And symbol lookup wasn’t working well. This seems to have fixed it.
saem
requested changes
Jul 18, 2023
Owner
saem
left a comment
There was a problem hiding this comment.
Thank you very much for the PR.
I can see how this might be an issue for some systems, but I don't want any config.nims. I'm hoping there are alternative ways to resolve this.
elijahr
pushed a commit
to elijahr/vscode-nim
that referenced
this pull request
Nov 29, 2025
* Adds syntax highlighting and lsp support to nimble files * Binds different APIs in preparation to implement custom macro expansion * More bindings
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was seeing errors like this in the Nim Language Server output:
Symbol lookup wasn’t working well with the lsp backend.
It's not documented but according to this stack overflow, configuration entries with type
arraymust nest the properties underitems.Additionally, when running
nimble vsixI was getting this error:This is because nimsuggest is not in the nim installation’s lib directory.
These changes explicitly add the nim installation’s root directory to the search path so that nimsuggest can be found when compiling.
On my system,
nim dumpin the vscode-nim directory gives these paths:But nimsuggest is located at /Users/user/.asdf/installs/nim/1.6.12/nimsuggest.