Re:Show HN: Markwhen: Markdown for Timelines
by mtoddsmith on Monday June 20, 2022 @01:44PM
(#31813229)
YYYY-DD-MM as a folder / filename does not sort correctly. Not a fan.
I much prefer YYYY-MM-DD for its sorting behavior.
Re:Show HN: Markwhen: Markdown for Timelines
by codetrotter on Monday June 20, 2022 @02:26PM
(#31813779)
Sorry, that was a typo. I meant to say YYYY-MM-DD. Edited now.
Re:Show HN: Markwhen: Markdown for Timelines
by eurasiantiger on Tuesday June 21, 2022 @01:31AM
(#31820248)
Important note: while a datestamp like YYYY-MM-DD does sort correctly, a datetime stamp such as YYYY-MM-DDThh-mm-ss does not because of DST and negative leap seconds.
Re:Show HN: Markwhen: Markdown for Timelines
by elromulous on Monday June 20, 2022 @04:29PM
(#31815472)
Where in Europe? I imagine this might vary by language / region. And could even differ in official use vs vernacular.
And ofc, the mixed order is the inferior option.
Re:Show HN: Markwhen: Markdown for Timelines
by codetrotter on Monday June 20, 2022 @07:33PM
(#31817661)
Norway
When a date is within the current year I state it as for example “27th of June”.
If weekday matters, and specific date is still relevant I’ll say for example “Monday 27th of June”.
I might also simply say “Sunday last week”, “Monday next week”, “Monday at the end of next month”, etc.
Likewise I might say “a couple of weeks ago”, “last week”, “a few days ago”, “in under two weeks”, etc.
Depends on context.
When including a date in a file name I prefer YYYY-MM-DD for date.
When using dates in a directory hierarchy I’ll have years on the top level, with months within them and dates within those.
Sometimes I might use a format like YYYY-mm-ddTHHMMz_s in a file name. For example “something_2022-06-20T1722+0000_1655745728_more_text.tbz”