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 processes run and complete, I guess it's checking the last changed timestamp against a cache somewhere, or something like that.
- Nimsuggest issue with the VS Code extension and nim 1.6.0 didlybom
- Nimsuggest issue with the VS Code extension and nim 1.6.0 rockcavera
- Nimsuggest issue with the VS Code extension and nim 1... enthus1ast
- Nimsuggest issue with the VS Code extension and n... jasonfi
