• ISO 8601 is paywalled
  • RFC allows a space instead of a T (e.g. 2020-12-09 16:09:…) which is nicer to read.
  • lolcatnip@reddthat.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    But $(date) does return a string with spaces, at least on every system I’ve ever used. And what’s so bad about the possibility of spaces in filenames? They’re slightly inconvenient in a command line, but I haven’t used a commuter this century that didn’t support spaces in filenames.

    • rtxn@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      11 months ago

      Bro, literally re-read the comment you replied to. It has an example of what might happen.

      • lolcatnip@reddthat.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        11 months ago

        Ok, I just reread it. I don’t see what you think I’m missing. You mean an improperly written find command misbehaving? The fact that a different date format could prevent a bug from manifesting doesn’t seem like much of an argument.

        • black0ut@pawb.social
          link
          fedilink
          arrow-up
          2
          ·
          11 months ago

          Spaces can exist in filenames. The only problem is that they have to be escaped. As the comment that you reread explained, cat hello world.txt would print the files hello and world.txt. If you wanted to print the file "hello world.txt" you’d either need to quote it (cat "hello world.txt") or escape the space (cat hello\ world.txt)