Comment on That'll be my last word

001100010010@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

• Ricaz@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Meanwhile Linux (ext4) users are over here sorting by whatever we want.

  With ctime, mtime and atime it doesn’t matter what you call your files!

  I use Arch btw

  source
• TWeaK@lemm.ee ⁨1⁩ ⁨year⁩ ago

  Strictly speaking in ISO 8601 it would be 2023-12-31.

  source

  • 001100010010@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    Yea lol, but missing some dashes will still work for for file sorting.

    source
• Zamotic@lemmy.zip ⁨1⁩ ⁨year⁩ ago

  I completely agree. Everyone always asks me why I suffix my filenames with the date like this (or YYYY.MM.DD). But this is so files sure up in correct order when sorted my name. It seems so obvious.

  source
• nero@lemmy.world ⁨1⁩ ⁨year⁩ ago

  How does that last point work? The ”Putting the date in the files ensures it wouldn’t disappear due to OS shenanigans.”?

  source

  • NessD@lemmy.world ⁨1⁩ ⁨year⁩ ago

    You create a file on 30.09.2010, back it up and lose it due to hardware failure on 12.07.2022. When you restore the file from your backup to your device it will most likely be stamped as created 12.07.2022 even though originally it was created before that. If you name your file manual_2010-09-30.pdf you always know the date it was created and sort it by that filename.

    source

    • nero@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Thanks for the example!

      source
  • 001100010010@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    Example:

    Lab_Report_20020101

    That’s what I always do with files. Windows like to reset your date attributes for some reason. If you copy a file, or upload it to cloud and redownload, there are some cloud services that doesn’t save the file date for some reason. Filename always gets saved.

    source