Follow the XDG Base Directory Specification

[danth]

What happened?

My home directory is on a network drive, so I have $XDG_CACHE_HOME pointing to a different filesystem that is stored locally, for performance reasons.

However, this extension currently ignores that environment variable and hardcodes its default value:

java/src/jdtls.rs

Lines 325 to 327 in b68357e

	Os::Linux => env_iter
	.find(|(k, _)| k == "HOME")
	.map(|(_, v)| PathBuf::from(v).join(".cache")),

What did you expect to happen?

I would expect this extension to follow the XDG Base Directory Specification, which the main Zed editor already does.

This simply means checking for $XDG_CACHE_HOME, and if it's set, using that path rather than $HOME/.cache.

Environment

Zed: 0.217.3
Platform: NixOS Xantusia 25.11.20251226.f560cce (Linux 6.12.63)

[tartarughina]

Hey @danth thanks for reporting.
The code you pointed at is a 1:1 port from the Python script used by JDTLS.

https://github.com/eclipse-jdtls/eclipse.jdt.ls/blob/main/org.eclipse.jdt.ls.product/scripts/jdtls.py#L86

I'll work on a solution based on your suggestion. If XDG_CACHE_HOME is set then it is going to take precedence over the path built from HOME.

Were you by any chance able to verify if jdtls works as intended once that cache path is respected?

[danth]

Unfortunately I've not been able to test this as I'm not familiar with how Zed extensions are compiled and loaded - otherwise I would have just implemented it myself and submitted a pull request :))

However I don't see any reason why it should not work.