Michael Härtl

Probably related: https://github.com/neoclide/coc.nvim/issues/1704. From what I understand they say, that the filetype is not reported correctly by the language server. But no idea where this should be fixed.

> The better approach might be to just preserve all whitespace as is. I'll look into this further. Great, thanks. Regarding markdown it's a bit over my head to be...

Ok, thanks for your helpful comments. So the formatting problem can only be fixed on the coc.nvim / coc-phpls side. If you find time I'd still appreciate any improvements with...

Related to / potential duplicate of #3046? @rgrunber Different to your issue I'm able to reproduce this error everytime. Is there anything else I can provide to help fixing the...

Unfortunately it's a private code base. jdtls is v1.35.0.

That's weird. I've installed jdtls via [mason-nvim](https://github.com/williamboman/mason.nvim). It clearly references the 1.35 download as can be seen in it's registry file here: https://github.com/mason-org/mason-registry/blob/8ae81b2226c0ebe27fcf433397ebd7ecca24aa9c/packages/jdtls/package.yaml

Here's the output of `jps -lv`. Note that I work on several Java projects in parallel each with different gradle versions. 640632 org.gradle.launcher.daemon.bootstrap.GradleDaemon -XX:MaxMetaspaceSize=1024m -XX:+HeapDumpOnOutOfMemoryError --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED...

I've now also tried with 1.36 and still get the same errors: ``` !SESSION 2024-06-11 19:22:43.805 ----------------------------------------------- eclipse.buildId=unknown java.version=21.0.1 java.vendor=Eclipse Adoptium BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Command-line arguments: -data...

I removed the content from that directory and now the gradle error is really gone, thanks. But the main problem is still there: > Java Model Exception: Error in Java...

I've added that setting now but no difference. Still see that exception in jdt.ls logs and the LSP does not work properly.