Thread with 17 posts

jump to expanded post

i had to add something to the PATH environment variable on Windows and i got the first few attempts wrong, and in the end had to look up how to do it... my pride... a thing my twenty-years-younger self could do, but not me... all these batch commands lost, like tears in rain...

Open thread at this post

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

Open thread at this post

one of my whimsical life regrets is that, as a kid, i understood that batch was a programming language, but i couldn't figure out how to write anything useful with it, because i didn't know where to look for documentation. imagine, imagine, i could've been a batch programmer!

Open thread at this post

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

Open thread at this post

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

Open thread at this post

@jernej__s something i should've clarified in the initial tweet is i specifically did not want to do a global state alteration like this! i'm familiar with the gui but didn't want to resort to it.

nice to see they've made it friendlier in newer versions, god knows it was a pain for so long

Open thread at this post