Why are there both TMP and TEMP environment variables? (2015)
devblogs.microsoft.com
Why are there both TMP and TEMP environment variables? (2015)
1–10 of 102 posts
Re: Why are there both TMP and TEMP environment variables? (2015)
#21995-ish. Telstra (Australia Telecom). Probably about 50k desktop computers across the organisation. One day a small file turned up in everyone's network home directory called null. A *nix person had evidently had a go at writing a .bat file.
Why do we need to adopt extant standards? (I was going to ask, why standardise? But realised that might confound the North Americans. : )
Re: Why are there both TMP and TEMP environment variables? (2015)
#3I didn't know it was such a chaos.
So I guess the moral of the story is: Ensure they always point to the same path, or else...
Re: Why are there both TMP and TEMP environment variables? (2015)
#41995-ish. Telstra (Australia Telecom). Probably about 50k desktop computers across the organisation. One day a small file turned up in everyone's network home directory called null. A *nix person had evidently had a go at writing a .bat file. Why do we need to adopt extant standards? (I was going to ask, why standardise? But realised that might confound the North Americans. : )
>One day a small file turned up in everyone's network home directory called null. A *nix person had evidently had a go at writing a .bat file
I assume that they first tried /dev/null which failed, so then moved onto just plain null?
Otherwise it would not make sense that a unix programmer did this. More likely ula dos programmer misspelled NUL as null.
Re: Why are there both TMP and TEMP environment variables? (2015)
#5> My recollection is that most CP/M programs were configured via patching. At least that’s how I configured them. I remember my WordStar manual coming with details about which bytes to patch to do what. There was also a few dozen bytes of patch space set aside for you to write your own subroutines, in case you needed to add custom support for your printer.
Huh. That is interesting, it was before my time, and I never heard of this :D
Re: Why are there both TMP and TEMP environment variables? (2015)
#6> My recollection is that most CP/M programs were configured via patching.
I honestly would have liked that better for a lot of programs than the dotfiles they litter all over my home directory.
Re: Why are there both TMP and TEMP environment variables? (2015)
#7> My recollection is that most CP/M programs were configured via patching. At least that’s how I configured them. I remember my WordStar manual coming with details about which bytes to patch to do what. There was also a few dozen bytes of patch space set aside for you to write your own subroutines, in case you needed to add custom support for your printer. Huh. That is interesting, it was before my time, and I never…
Yes, it was definitely a thing. The patching code had to be in Z80/8080 machine code. I wrote higher performance keyboard and display routines for my copy of Wordstar using this feature.
Re: Why are there both TMP and TEMP environment variables? (2015)
#8always shove it to `%LOCALAPPDATA%/Temp`, or `~/AppData/Local/Temp`, and don't think otherwise
Re: Why are there both TMP and TEMP environment variables? (2015)
#9> My recollection is that most CP/M programs were configured via patching. I honestly would have liked that better for a lot of programs than the dotfiles they litter all over my home directory.
Yea this is something I'd love to see standardised, a distro that was able to enforce a .config folder somehow would be a winner for me. Think weve probably missed the boat though.
Re: Why are there both TMP and TEMP environment variables? (2015)
#101995-ish. Telstra (Australia Telecom). Probably about 50k desktop computers across the organisation. One day a small file turned up in everyone's network home directory called null. A *nix person had evidently had a go at writing a .bat file. Why do we need to adopt extant standards? (I was going to ask, why standardise? But realised that might confound the North Americans. : )
>One day a small file turned up in everyone's network home directory called null. A *nix person had evidently had a go at writing a .bat file I assume that they first tried /dev/null which failed, so then moved onto just plain null? Otherwise it would not make sense that a unix programmer did this. More likely ula dos programmer misspelled NUL as null.
I've already created a 'NULL' file, but it was not a Unix thing... It was just because I got confused if it was NULL as in the programming languages I usually use.