All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Why Windows has both TMP and TEMP environment variables: A history of parallel evolution

By

Raymond Chen

29d ago· 5 min readenInsight

Summary

This article explores the historical reason why Windows (and earlier systems) have both TMP and TEMP environment variables pointing to temporary file locations. It traces back to the CP/M operating system from 1973, which had no environment variables, and explains how different operating systems and software ecosystems evolved in parallel — some adopting TMP, others TEMP. The article explains that both exist due to legacy compatibility and that modern Windows treats them as equivalent, with neither being more "right" than the other.

Key quotes

· 3 pulled
If you snoop around your environment variables, you may notice that there are two variables that propose to specify the location of temporary files.
The CP/M operating system had no environment variables. That sounds like a strange place to start a discussion of environment variables, but it's actually important.
Since it had no environment variables, there was consequently neither a TMP nor a
Snippet from the RSS feed
Parallel evolution.

You might also wanna read