Hacker News new | ask | show | jobs
by idbfs 1834 days ago
I knew what this was going to be as soon as I saw "aux.h" in the screenshot.

Some years ago I was working on an embedded system that involved DisplayPort. For those unaware, DP's control channel is called AUX. One day, my new co-worker who used Windows asked me, who used Linux, why my AUX-related code wasn't checked in - which it most certainly was.

And that, folks, is how I learned about this absurd property of Windows that exists to this day.

3 comments

I thought it was going to be "not a typewriter" [1] but I should have known, because 1974 is too late.

[1] https://en.wikipedia.org/wiki/Not_a_typewriter

OS filename issues and checking in code reminds me of an 8-hour mess I got myself into due to OS X deciding that filenames are case-insensitive, and git knowing that they are not...
I have had funny experiences copying files from Linux to a NTFS partition, because NTFS is actually case-sensitive, but Windows itself is not, so you suddenly end up with two files that differ only by case and you can't delete or rename them (but funnily enough they show fine on Explorer).
Comedy. FWIW, git mv works on Windows for case-respecting renames
Yup, if I recall correctly the undeletable hidden file that git created was part of the issue.
It's all just a con.

C:\>echo foo > con

foo

I still use copy con on a regular basis to quick and dirty create files.