Go the the Extensions tab in the sidebar. Click the Settings icon in the Nim
extension tile, and click on Extension Settings in the menu that displays. The
3rd setting is Nim: Enable Nimsuggest, just uncheck that option.
it's an old issue
basically the extension doesn't know which file is the root/main of your
project, so it has to open a nimsuggest file for each .nim file you open/edit.
Question is why those processes not always die automatically when files are
closed.
You can do 2 thigs:
* proper one: as
Actually, it seems that I was wrong and this happens with nim 1.4.8 as well. It
just took a bit longer for it to happen. I'm trying the typescript based VS
Code extension to see if that one works better.
you need to specify a project file via the "nim.project" setting.
How do you disable nimsuggest on the VS Code nim extension? I did not find it
in the documentation of the extension...
This happened to me when doing a lot of find/replace across many files. The
more files, the more nimsuggest processes were launched. It helped to let them
complete down before proceeding. The solution is to turn off the feature when
changing many files at once. Then turn it back on, but let the
Had similar issues with the (typescript) vs code plugin, it used a whole core,
I've disabled nimsuggest altogether.
I noticed this yesterday when trying to use the vscode extension written in
Nim. It opened a bunch of nimsuggest.exe processes. With the typescript
extension this problem does not occur.
I believe there may be some problem in the extension. I didn't have a lot of
time to check it out.
I am running into serious issues with nim 1.6.0 when using VS Code. VSCode
seems to be creating a lot of nimsuggest processes which never end, resulting
on my windows PC running out of memory and crashing after a while.
Checking with process explorer I can see that on the process tree the code.e
