Closed nueropath closed 1 year ago
Interesting... I can replicate the behavior you are seeing with 6.2.2 on Windows. If I install 6.2 on Windows, it works as expected. The fix for the issue on MacOS shouldn't have impacted any other platforms' builds, so I'm going to need to do a little digging into what caused the regression.
If you would like a workaround for 6.2.2 on Windows:
C:\Program Files (x86)\UCBLogo
).LOGOLIB
folder.RENAME-GRAVE-ACCENT
to a literal backtick `
RENAME-NUMBER-SIGN
to a literal number sign #
Interesting... I can replicate the behavior you are seeing with 6.2.2 on Windows. If I install 6.2 on Windows, it works as expected. The fix for the issue on MacOS shouldn't have impacted any other platforms' builds, so I'm going to need to do a little digging into what caused the regression.
If you would like a workaround for 6.2.2 on Windows:
1. Go to the install folder (by default, this would be `C:\Program Files (x86)\UCBLogo`). 2. Open the `LOGOLIB` folder. 3. Rename the file `RENAME-GRAVE-ACCENT` to a literal backtick `` ` `` 4. Rename the file `RENAME-NUMBER-SIGN` to a literal number sign `#`
much appericated for the workaround. It now works as expected.
Running the following command in ucbLogo 6.2.2 on windows,
I get:
while the expected output from CSLS is:
It seems this bug had occured before on MacOS #117.