it's not really that surprising however, over time
export PATH=$PATH:/foo/bar
would naturally supplant
set PATH=%PATH%;C:\foo\bar
simply because the former has vastly more day-to-day relevance to my life now; the last time i did the latter, it was on MS-DOS
i'm having a bit of a berenstain bears effect with believing that %variable% was surely never how MS-DOS did variable substitution (surely it's some newfangled Windows NT thing?!), but here it is in the MS-DOS 5.0 manual!
From the bitsavers.org collection, a scanned-in computer-related document.microsoft :: msdos 5 :: Microsoft - MS-DOS 5.0 Users Guide and Reference 1991
APPENDING PYTHON TO MY PATH DIDN'T WORK BECAUSE IT HITS THE FAKE PYTHON.EXE BUNDLED WITH WINDOWS THAT BRINGS UP THE MICROSOFT STORE PAGE!!!
the tanks roll on redmond tomorrow. you have my word. there will be no quarter
while you're here, here's a useful tip:
you don't have to modify the global PATH on Windows! the familiar bash export + source trick has an equivalent for batch files: you use set and then run the batch file normally within a cmd session. idk what to do for PowerShell
@hikari environment variables in powershell are accessed through $env:VARIABLE_NAME and work the same as any other variable
which is actually sort of nice but only if you can remember it
@whitequark @0xabad1dea @hikari I think it's better with curl because at least curl doesn't change that much. sure, your version might be ancient, and sure, it might make some corporate audit scanners really angry, but mostly it's fine
but python? most people don't appreciate having an ancient version of python