Fred Snyder

The SocketProvider's primary purpose is to acquire an available port to avoid conflicts, e.g., if you're running multiple VS Code windows. If we add an option to specify the port,...

@RtypeStudios If you can work with me on a patch, I'm happy to merge it into the extension. You seem like a good subject matter expert where Docker is involved....

The (slightly misnamed) `stdio` branch adds two new configuration options: `solargraph.transport`: Either `socket` or `external`. If set to `external`, the extension will connect to an existing server instead of starting...

This feature is now in the master branch. The supported transports are socket, stdio, and external. The configuration to connect to an external server should look something like this: ```...

@RtypeStudios 2 issues I see: 1. The `solargraph.transport` and `solargraph.externalServer` configurations belong in the VS Code settings (File -> Preferences -> Settings), not the .solargraph.yml file. 2. The external port...

Version 0.18.0 is released with the `solargraph.transport` and `solargraph.externalServer` options.

@MilanJansenOGD Are there any more detailed error messages in the developer console (Help -> Toggle Developer Tools)?

Do you get a backtrace in the debug console (Help -> Toggle Developer Tools)?

I'll look into it, but one workaround is to use indentation instead of ticks: ```ruby # If no block is given, an Enumerator is returned instead. # # 5.downto(1) ```...

One possible issue is that definitions aren't supported for the Ruby core and stdlib. They should work for your own code and most gems.