Starting from 6.8.2, jdtls runs with errors.

[mylvghb]

Relevance Confirmation

• I confirmed that this is not an issue with the Eclipse JDT Language Server itself

What happened?

What did you expect to happen?

Can run and work normally.

Environment

Zed: 0.217.3
Platform: Windows 11 Version 24H2
Java: 25.0.1 2025-10-21 LTS

[tartarughina]

Could you please update to the latest version 6.8.3 to confirm you are still incurring into this issue?

[kenzson]

Language server jdtls:

from extension "Java" version 6.8.3: 文件名、目录名或卷标语法不正确。 (os error 123)

[tartarughina]

@kenzson are you too on Windows?

@mylvghb could you please check what's not available in the java extension work directory that the extension assumes should be instead?

[mylvghb]

@tartarughina The same project runs without any issues using v6.8.1.

[mylvghb]

@tartarughina This issue might be caused by commit a540253.

[tartarughina]

@mylvghb thanks for sharing that. Very likely the issue is due to that. Quoting may have specific edge cases where escaping the space is preferred

[mylvghb]

Waiting for the fix.

[nikosszzz]

I am also getting this error. Windows 11 25H2. v6.8.1 works.

[tartarughina]

Hey @nikosszzz @mylvghb @kenzson, I've published #161. Before merging it could you give it a try and letting me know if the issue is fixed for you? I've tested it on my Windows machine but I'd love to get also your feedback.

[mylvghb]

@tartarughina I cloned your repository and installed the development extension, but the problem still persists.

log: 2025-12-23T10:14:48+08:00 ERROR [project::lsp_store] Failed to start language server "jdtls": from extension "Java" version 6.8.3: 文件名、目录名或卷标语法不正确。 (os error 123)

[mylvghb]

@tartarughina

pub fn path_to_quoted_string<P: AsRef<Path>>(path: P) -> zed::Result<String> {
    let path_str = path
        .as_ref()
        .to_path_buf()
        .into_os_string()
        .into_string()
        .map_err(|_| PATH_TO_STR_ERROR.to_string())?;

    Ok(path_str)
}

Just return Ok(path_str) directly instead of calling format_path_for_os, and it works fine. If quotes are redefined to mean that the path begins and ends with a quote, then such a path is invalid.