I am on Windows 10.
Also I tried to check environment variables are listed but was greeted with another error message.
PS C:\Users\21910478> set
cmdlet Set-Variable at command pipeline position 1
Supply values for the following parameters:
Name[0]:
Set-Variable : Cannot bind argument to parameter 'Name' because it is an empty array.
At line:1 char:1
+ set
+ ~~~
+ CategoryInfo : InvalidData: (:) [Set-Variable], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyArrayNotAllowed,Microsoft.PowerShell.Commands.SetVariableCommand
Well guys it worked someway or other. I cannot thank everyone enough for their suggestions. And of course special thanks to @ufechner7 for the finding the last piece of puzzle.
I suppose you were trying to go into the package mode with ], and it works in non-dumb terminal (as I guess you discovered), not in what you had, but I’m unsure what you were trying with “j?”:
For the help mode you must first press ? then type what you want help for, but something more than just “j”.
Are these terminal issues standard for Windows users? If so, Julia installation depends on first setting up an appropriate terminal. That would be bad.
They are not. Usually the TERM variable is not set on Windows. But there are exceptions, for example an old Perl version used to set it to “dumb” when installing it.
You can no longer buy Windows 10 or older, and this isn’t a problem for Windows 11, I understand (that has Windows terminal, except some early first version of it).
I made a PR for Julialang.org website for Windows maybe clarifying this (also recommending 64-bit, which is anyway they only thing supported in Windows 11; it feels unhelpful by now to mention that 32-bit version works for 32-bit and 64-bit even is strictly true).
If there are any instructions for Windows 10 or older that need to be clarified, please suggest at my PR.