Timeline for Unix file naming convention
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 25, 2011 at 19:37 | comment | added | BillThor | @ultrasawblade Thanks, shows how often I script Windows. I tried to skip the rarer executable extensions like cmd, pif, vb*, wsh, and the rest of them. | |
| Feb 25, 2011 at 19:32 | history | edited | BillThor | CC BY-SA 2.5 |
Added scr to windows executable list.
|
| Feb 25, 2011 at 0:17 | comment | added | LawrenceC | .scr is also a Windows executable extension. | |
| Feb 14, 2011 at 17:16 | comment | added | BillThor | @Mikel I also program Java where CamelCase is a convention. Sometimes patterns and conventions conflict. | |
| Feb 14, 2011 at 3:03 | comment | added | Mikel | It's not "bad" versus "good". It's "this is how it's usually done". It's a convention the OP was asking for. The reason? It could be because Unix people don't like pressing Shift, it could be because old systems only had UPPERCASE, or for another reason. I'm not sure. | |
| Feb 13, 2011 at 21:46 | comment | added | Mikel | CamelCase is an anti pattern on Unix. The OP was asking about conventions. | |
| Feb 13, 2011 at 16:42 | history | edited | Steven D | CC BY-SA 2.5 |
added 6 characters in body
|
| Feb 13, 2011 at 16:09 | history | answered | BillThor | CC BY-SA 2.5 |