nested HOME variable not resolved

[Bananeweizen]

Version

6.9.0

Operating System

Windows

Eclipse version

2023-12

Bug description

One user in my team sometimes gets trouble with the HOME variable, which then leads to all kind of funny configuration issues.

Actual behavior

The HOME variable can be defined by other nested variables, and sometimes that double level of variables is resolved correctly, and sometimes not. In the bad case the configuration looks like this:

If the 2 variables in there would be resolved again, the path would be correct.

Expected behavior

I'm aware that even in batch files running in cmd.exe the order of evaluation is hard to estimate correctly, therefore nested variables can fail there, too. We could probably improve this in egit by doing a repeated evaluation. However, that would be more complex than the first System.getenv() call, because we would have to somehow parse the return value and recognize the variables in there.

Or is someone aware of other settings that might influence whether and how nested environment variables are resolved correctly?

Relevant log output

No response

Other information

No response