Well. It looks like somebody’s bug nevertheless.
These are not the days of MS-DOS anymore, and I believe that W10 has a clear notion of “user home”.
Cheers — MA
On Jun 20, 2017, at 15:52 , Mirko Vukovic mirko.vukovic@gmail.com wrote:
On Tue, Jun 20, 2017 at 3:02 AM Mark Evenson evenson@panix.com wrote:
On 6/17/17 10:12, Marco Antoniotti wrote:
Well. Looks like a bug in ABCL USER-HOMEDIR-PATHNAME to me.
This is not an ABCL bug. Thanks to Olof-Joachim's instructions:
CL-USER> (jstatic "getProperty" "java.lang.System" "user.home") "C:\WINDOWS\system32\config\systemprofile"
in accordance to the documentation. I now need to figure out why Java and ABCL think that "user.home" is "C:\WINDOWS\system32\config\systemprofile". It may be something in the computer setup that was modified last week by our IT.
PS - I never thought it was a bug, but wanted to dig a bit deeper into my JVM environment.
ABCL's [USER-HOMEDIR-PATHNAME][1] quite clearly directly uses the value of 'user.home' Java system property.
From [Section 2.2 of the manual][manual]:
The user’s home directory is determined by the value of the JVM system property 'user.home'. This value may or may not correspond to the value of the HOME system environment variable, at the discretion of the JVM implementation that ABCL finds itself hosted upon.
I don't see that the current behavior is a bug in ABCL, but rather the result of the JVM implementation that you are running.
If y'all see this is a bug, how would you have us "fix" it?
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
-- Marco Antoniotti