Our great sponsors
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
LanguageServer.jl
An implementation of the Microsoft Language Server Protocol for the Julia language.
Statically lint = find errors in the Julia file like using variables that are not defined, and functions with the wrong arguments. For Julia, StaticLint.jl is an actively developed library that does static linting. It basically provides a bunch of functions that spit out errors in your Julia file like those that I mentioned above. If you are an Emacs editor user, this project is like a "convenience" which will run Julia silently in the background, and communicate with it to extract errors in the file that you currently have open. These errors are then highlighted in your editor view using the Flycheck package that is one of the ways to highlight errors in Emacs.
You can find my setup here. Yes, the autocomplete is good enough for my purposes. I don't use VSCode so can't compare - but I've got autocomplete running in Emacs and it mostly behaves as I would expect. Keep in mind that LanguageServer.jl is still under development, so some autocompletion fails fundamentally because of the backend - in other words, some things currently won't work in any editor, I think.
I believe that LanguageServer.jl actually uses StaticLint, which means that there is no difference. Ideally, there would be a LanguageServer implementation for Julia which reliably communicates the information from StaticLint to Flycheck. I am using lsp-julia, but this seems to not show the errors from StaticLint. I am aware of eglot-jl but I could not get it to work... So this package is basically like an "error server" that has worked for me to finally get static errors to show up in Emacs for Julia.