Lucas Alber

I did not. Wasn't really sure if it is a LSP or Emmet Bug (or both).

Nothing correlated is logged. But I should mention that LSP complains that the file isn't inside window folders. That is the only message logged, besides deletes and character inserts.

> > > Connection to the debugger works. But I am getting a "missing mainClass..." error. Thats fixed by supplying: ```json "mainClass": "${file}", "modulePaths": ["${folder}"] ``` Now the Debugger fails...

Okey, I found the comment in `terminal_process.py`. Seems like ST4 does not support runInTerminal?

> "console": "internalConsole" In this case the Server errors with: ``` jdtls: 08.03.2021, 23:12:44 Error parsing message: com.google.gson.JsonSyntaxException: Expected a com.google.gson.JsonObject but was com.google.gson.JsonNull Expected a com.google.gson.JsonObject but was com.google.gson.JsonNull...

> > > What request is this failing on? If its the initialize request its likely there are additional required parameters in the configuration that get patched in. > >...

> > > Looks to be way past the initialize request. From the looks of it they are just not handling the configurationDone request correctly and treating the arguments as...

It's working now. Although I am still getting ``` Error parsing message: com.google.gson.JsonSyntaxException: Expected a com.google.gson.JsonObject but was com.google.gson.JsonNull ``` Settings: ``` { "type": "java", "name": "Launch", "request": "launch", "mainClass":...

Fixed that too. Since I changed the Protocol to `{}` instead of `None`, this may break other things?

@daveleroy How would an adapter add/set configuration variables? I would like to fetch classpath, mainclass,... with the Language Server because for example classpath can get very complicated on a big...