qaz to Memes@lemmy.ml • 11 months agoStandards shouldn't be behind a paywalllemmy.worldimagemessage-square100fedilinkarrow-up1661arrow-down134file-textcross-posted to: iso8601@lemmy.sdf.org
arrow-up1627arrow-down1imageStandards shouldn't be behind a paywalllemmy.worldqaz to Memes@lemmy.ml • 11 months agomessage-square100fedilinkfile-textcross-posted to: iso8601@lemmy.sdf.org
ISO 8601 is paywalled RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
minus-square@calcopiritus@lemmy.worldlinkfedilink1•11 months agoBoth arguments are surrounded by ", which should be space-safe. At least in the shells I use, putting " makes spaces inside paths a non-issue.
minus-square@rtxn@lemmy.worldlinkfedilinkEnglish1•11 months agoFor the rsync command, yes. But this: for d in $(find . -type d); do echo "$d" done will process the space-separated parts of each path as separate items. I had to work around this issue just two days ago, it’s an obscure thing that not everyone will keep in mind.
Both arguments are surrounded by
", which should be space-safe.At least in the shells I use, putting
"makes spaces inside paths a non-issue.For the
rsynccommand, yes. But this:for d in $(find . -type d); do echo "$d" donewill process the space-separated parts of each path as separate items. I had to work around this issue just two days ago, it’s an obscure thing that not everyone will keep in mind.