Mirror of forum.nim-lang.org

13809 :: How should I do to trigger diagnostics check right after opening vscode.

• KevinLenz (orginal) [2026-03-23T16:20:24+01:00] view original

  Now only when I edit the file can it send diagnostics request to lsp

  There's the consequent problem: Several long files' refactor hasn't been done before, but now open the project again the diagnostics won't automatically run. It need me to do a little move: an editing to trigger the diagnostics request's sending(means no red underwave could be shown right after I open vscode). I'm using vscode-nim-lsp(vscode extension) + nimlsp

  When I reopen a middle scale project, I have to edit a char in every files one by one, because I don't remember which files have I edited and not completed before.

  There seems to be no configure option in the extension to set 'do diagnostics when open vscode/project'

---

• KevinLenz (orginal) [2026-03-23T16:46:16+01:00] view original

  diagnostics towards nim is nimsuggest chk I want auto whole project's files' nimggest chk right after opening vscode

---

• KevinLenz (orginal) [2026-03-24T02:47:52+01:00] view original

  I tried Zed Editor and saw the rpc log. It shows that my editor receives "method":"textDocument/publishDiagnostics" from lsp only after my editor sends "method":"textDocument/didSave" with the whole single file content attached in json

---

• KevinLenz (orginal) [2026-03-24T05:39:15+01:00] view original

  I haven't regarded how nim files are detected by vscode. Maybe files in my project folder (even already with .nimble file) are detected as single files rather than files in project, so that as vscode opens but doesn't request lsp and nimsuggest to give out every files' diagnostics.

---