Mirror of forum.nim-lang.org

3790 :: VS Code linting broken?

• Lando (orginal) [2018-04-30T09:56:25+02:00] view original

  I use Visual Studio Code with the Nim plugin and automatic code checking stopped doing anything a while ago, meaning I don't see red error markers anymore when I type nonsense. Didn't change the config (files.autoSave is "afterDelay", nim.lintOnSave is true) and there's apparently no related issue in the plugin's github tracker. Does anybody else have this problem or am I missing something? Nimsuggest functions auto-completion and doc-popups work.

---

• nucky9 (orginal) [2018-04-30T18:21:51+02:00] view original

  I actually had the opposite problem a few days ago (auto-completion and doc-popups not working, but error highlighting was). Everything is working now though, and I didn't try to do any troubleshooting at the time, so I have no idea what fixed it (possibly a system reboot, but I can't say for sure).

  For reference, my VS Code is the latest version (1.22.2), and I'm using Nim 0.18.0.

---

• honhon (orginal) [2018-05-01T03:25:24+02:00] view original

  Maybe restart vscode or check that there are not any nimsuggest servers still running/crashed.

---

• Lando (orginal) [2018-05-01T13:46:58+02:00] view original

  @nucky9: same versions of VS-Code and Nim here.

  @honhon: checked for leftover/crashed nimsuggest instances, none found. Vs-Code's Nim plugin starts multiple nimsuggest instances, one for every

  EDIT:

  folder (Nim package) in the workspace. <-- WRONG

  source file for which nimsuggest functions are used. <-- CORRECT

  The problem remains even after a fresh install of Nim and VS-Code.

  Narrowed it down: code checking only works for the first folder in the workspace. So my on-the-fly "fix" is to drag the folder to the top position in the explorer panel...

---