Timeline for OS X filesystem case insensitivity corrupts vlc command
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2016 at 20:29 | answer | added | webappzero | timeline score: 0 | |
| May 25, 2016 at 19:54 | vote | accept | webappzero | ||
| May 25, 2016 at 19:57 | |||||
| May 25, 2016 at 19:42 | history | edited | Celada | CC BY-SA 3.0 | Fixed title: it's the filesystem, not the terminal, that is case insensitive. |
| May 25, 2016 at 19:15 | history | edited | webappzero | CC BY-SA 3.0 | Add to explanation. |
| May 25, 2016 at 17:41 | comment | added | DisplayName | What happens when you run type instead of which? Same results? | |
| May 25, 2016 at 17:32 | answer | added | Ryder | timeline score: 3 | |
| May 25, 2016 at 16:38 | comment | added | thrig | It's the filesystem that's case-insensitive, not the terminal. Meanwhile, most everything else (e.g. the C VLC is written in) is case sensitive. | |
| May 25, 2016 at 16:36 | comment | added | Wildcard | If the calling command is referenced from inside the application as anything other than a filename, it wouldn't be automatically case insensitive. | |
| May 25, 2016 at 16:17 | history | asked | webappzero | CC BY-SA 3.0 |