Timeline for Reserved characters in file names
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2012 at 16:24 | comment | added | Ernest A C | @Random832 Yes, probably I should do that. | |
| Oct 1, 2012 at 15:14 | comment | added | Random832 | "I'm writing a shell script that requires the user to type a file name and I would like to make sure the name doesn't have any invalid characters. Is there a list somewhere?" Just try to create the file, and fail cleanly and tell them if it didn't work. There are other reasons file creation could fail (creating under a nonexistent directory, for example), and trying to check for all of them in advance just opens you to a race condition. | |
| Oct 1, 2012 at 14:21 | history | edited | daisy |
edited tags
|
|
| Oct 1, 2012 at 13:29 | vote | accept | Ernest A C | ||
| Oct 1, 2012 at 13:27 | comment | added | Ernest A C | @JimParis you were right. | |
| Oct 1, 2012 at 13:24 | history | edited | Ernest A C | CC BY-SA 3.0 |
update with new information
|
| Oct 1, 2012 at 7:07 | comment | added | Marco | Also interesting in this context: Understanding Unix file name encoding | |
| Oct 1, 2012 at 4:43 | comment | added | jordanm | @JimParis Do you have an example of a *nix filesystem that doesn't allow characters other than \0 and /? | |
| Oct 1, 2012 at 2:51 | comment | added | Jim Paris | Which characters are allowed or disallowed depends on the filesystem in use. | |
| Oct 1, 2012 at 1:43 | answer | added | user732 | timeline score: 6 | |
| Oct 1, 2012 at 0:02 | history | edited | daisy | CC BY-SA 3.0 |
edited title
|
| Sep 30, 2012 at 23:58 | answer | added | daisy | timeline score: 1 | |
| Sep 30, 2012 at 23:38 | history | asked | Ernest A C | CC BY-SA 3.0 |