Timeline for What characters might be used to substitute for colon in folder names using a time-of-day? [closed]
Current License: CC BY-SA 3.0
18 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 11, 2020 at 12:51 | history | closed | bmike♦ | Opinion-based | |
Feb 3, 2020 at 20:24 | answer | added | Robert | timeline score: 6 | |
S Mar 26, 2018 at 10:59 | history | suggested | CommunityBot | CC BY-SA 3.0 |
Grammar and typos
|
Mar 26, 2018 at 10:35 | review | Suggested edits | |||
S Mar 26, 2018 at 10:59 | |||||
Mar 28, 2016 at 1:19 | vote | accept | Basil Bourque | ||
Jan 6, 2016 at 0:13 | answer | added | rocky | timeline score: 1 | |
Dec 11, 2014 at 21:37 | history | edited | Basil Bourque | CC BY-SA 3.0 |
added 172 characters in body
|
Dec 11, 2014 at 21:34 | comment | added | Basil Bourque | @Mark I'm programming Java and Objective-C. See updated Question. | |
Dec 11, 2014 at 13:02 | comment | added | mmmmmm | @BasilBourque what programming access are you using? | |
Dec 11, 2014 at 12:38 | history | tweeted | twitter.com/#!/askdifferent/status/543021891590840320 | ||
Dec 11, 2014 at 3:32 | answer | added | Omar Vasquez | timeline score: 8 | |
Dec 11, 2014 at 3:27 | comment | added | ganbustein | Specifically, HFS+ allows filenames to contain / but not colon. When in Terminal (or anywhere the filesystem is accessed using the POSIX API instead of the Macintosh API), the / in the name as stored on disk is translated to : in RAM, and : in RAM is translated back to / as a new filename is stored in the catalog. Programs using the traditional Macintosh API are not affected, and see the / just as it appears on disk. This way each API has only a single forbidden character (well, two if you count NUL) and only a single filename separator, without interfering with each other. | |
Dec 11, 2014 at 2:59 | comment | added | 0942v8653 | I've never had any trouble accessing a file with a colon in the name. It just looks weird from Finder, since it's switched to a slash. | |
Dec 11, 2014 at 1:47 | answer | added | Kent | timeline score: 7 | |
Dec 11, 2014 at 0:52 | comment | added | Basil Bourque | @Mark Modern versions of the Finder may handle a colon. But during programmatic access, problems ensue. | |
Dec 11, 2014 at 0:31 | comment | added | mmmmmm | Why not just use the : it seems to work OK from the shell. I suspect only OS<=9 and classic have an issue with : so nowadays is an issue. AL:so MS OSes can use / as a directory split | |
Dec 10, 2014 at 23:48 | comment | added | Brian Duke | Pretty much all modern file systems support spaces in file names. Also, if readability isn't a concern why not just eliminate the offending characters and use a set format, ex.:YYYYMMDDTHHMMSSZ. | |
Dec 10, 2014 at 23:31 | history | asked | Basil Bourque | CC BY-SA 3.0 |