Timeline for Push onto array with find exec
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2015 at 21:27 | vote | accept | AmadeusDrZaius | ||
| Mar 9, 2015 at 21:27 | comment | added | AmadeusDrZaius |
Thanks for the confirmation. This answer made it sound as though NUL was allowed on Mac, but I guess it's just allowed by HFS+, but not by the OS.
|
|
| Mar 9, 2015 at 21:25 | comment | added | Valentin Bajrami |
@AmadeusDrZaius This aproach does force read to use NUL byte as it's line delimiter. Since NUL is not a valid byte in unix filenames, this however is the safest place of feeding an array. See mywiki.wooledge.org/BashFAQ/020 for a better explanation.
|
|
| Mar 9, 2015 at 21:22 | comment | added | Michael Homer | File names cannot have null bytes in them. Bash strings also cannot contain nulls. | |
| Mar 9, 2015 at 21:18 | comment | added | AmadeusDrZaius |
My original intent with the array was to allow the NUL character in a filename. From what I can tell, this approach does not allow them. Is that right?
|
|
| Mar 9, 2015 at 21:00 | history | answered | Valentin Bajrami | CC BY-SA 3.0 |