Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LSP error with VSCode and config.nims file #89

Open
JuanCarlosllh opened this issue Nov 29, 2024 · 0 comments
Open

LSP error with VSCode and config.nims file #89

JuanCarlosllh opened this issue Nov 29, 2024 · 0 comments

Comments

@JuanCarlosllh
Copy link

Hello! I’m testing this package, and it works wonderfully, but there's an issue with the Nim LSP and VSCode that I can’t resolve.

I believe this might be a configuration issue in my editor, but since the example in this repo is configured for VSCode, I expect it to work correctly with the official Nim extension.

The LSP doesn’t work due to the following error:

syncio.nim(767)          open
Error: unhandled exception: cannot open: /Users/juancarlosllh/Projects/Playdate/hello_world_nim/playdate/bindings/malloc.nim [IOError]

This error causes the LSP to restart, and features like autocomplete, go to definition, etc., stop working.

The issue seems to be caused by the config.nims file. If I comment out the line include playdate/build/config in this file, the LSP works correctly.

A workaround is to comment out this line when the editor starts. After that, if I uncomment it, everything works as expected.

I'm using VSCode 1.95.3 with the official nim-lang.org extension, Nim 2.20.0 and Nimble 0.16.1

@JuanCarlosllh JuanCarlosllh changed the title Error with Nim Lsp and VSCode with config.nims LSO error with VSCode and config.nims file Nov 30, 2024
@JuanCarlosllh JuanCarlosllh changed the title LSO error with VSCode and config.nims file LSP error with VSCode and config.nims file Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant