undefined | Better HN

0 pointsveidr4y ago0 comments

Thanks! Indeed the blog post omitted that step, probably since they already had it installed or something.

Once I installed the base LSP package, and restarted Sublime, then it gave me an error[1] at startup, explaining that it couldn't initialize the LSP for TypeScript. The error message included a button to fix it.

After that, yeah, it works a lot better! Jump to definition works, and the as-you-type errors I mentioned before now do appear. Also, the auto-complete list looks fairly sane, without all the "random guesses from all the text in this project" entries it had before.

So... not bad! At a glance I think it is still probably not as good a VS Code, but it might be usable. I will give it a closer look later.

[1] The error was: "Could not start LSP-typescript due to not being able to find Node.js runtime on the PATH. Press the "Install Node.js" button to install Node.js automatically (note that it will be installed locally for LSP and will not affect your system otherwise)."

0 comments

2 comments · 1 top-level

tehnub4y ago· 1 in thread

What are your thoughts on as-you-type errors? I personally don't like seeing errors on every keystroke, so in sublime, I set the lint mode to "background" and set the "delay" [0] to 2 or 3 seconds. Do you know if such a thing is possible in vscode?

[0]: https://www.sublimelinter.com/en/v3.10.10/global_settings.ht....

veidrOP4y ago

My own thoughts on it are that yes, that is definitely something that should be user-controllable, but as far as I know it's not possible in VS Code. I remember the old issue below, which was closed without actually fixing that.

Personally, though, I've learned to live with it, so it no longer bothers me, except in principle. ;-)

I'd much rather have annoyingly-instant error highlighting than missing or incomplete error highlighting. It will look good once I've finished the code.

https://github.com/microsoft/vscode/issues/74798

j / k navigate · click thread line to collapse