6 ms·
Why doesn't Windows drop the purported compatibility with CP/M and get rid of control-z being a special file marker at this point? Lots of legacy code relying o
by jokh 8y ago
Why doesn't Windows drop the purported compatibility with CP/M and get rid of control-z being a special file marker at this point? Lots of legacy code relying on it?
- Thorrez 8y agoSomeone could even write new code that relies on it.
- Arnavion 8y agoFWIW it's generally advised to not open files in text mode on Windows anyway. The handling of \x1A is one reason. The automatic mangling of newlines into Windows newlines is another. Edit: And while cmd's type does process it, modern stuff like PS's Get-Content does not.
- JdeBP 8y agoIt's not in Windows in the first place. The headlined article does explicitly say this. It's library code in a large number of applications programs. * http://jdebp.eu./FGA/dos-character-26-is-not-special.html http://jdebp.eu./FGA/dos-character-26-is-not-special.html