71–80 of 102 posts
Note that Mermaid also supports timelines (if it is new enough): https://mermaid.js.org/syntax/timeline.html Mermaid is supported by gitlab/github and other markdown editors (within code blocks).
The charts you linked don't look like the same kind of chart to me. There's information about what happened after what, but the information about how much each task took seems missing.
Earlier quoted context omitted.
Because this is ISO 8601 date format, the standard date format that intentionally uses dashes to not confuse 25/01/22, 01/22/25 and 22/01/26 which are the same date in different formats (that's why it uses dashes for dates, as for why it uses / for interval I have no idea)
I know ISO 8601, but that doesn't answer my question. Let me rephrase this, why was a format intuitive to a machine chosen instead of a format which feels more intuitive to a human? I think YYYY/MM/DD - YYYY/MM/DD will mean the correct thing to many more people than YYYY-MM-DD / YYYY-MM-DD, which I suspect many will interpret as an OR and not a RANGE.
I create a "Markwhen" folder and create a "test.mw" not there, but it doesn't render, and I can't an option for preview in the command palette.
Creator here - glad to see people like markwhen! Been working on markwhen for a few years now, originally inspired by cheeaun's life timeline that another commenter posted about. At this point markwhen is available as a VS Code extension, Obsidian plugin, CLI tool, and web editor in Meridiem. Some recent markwhen developments: - Dial, a fork of bolt.new (Stackblitz's very cool tool that leverages AI to help quickly s…
Things like Markdown work because they are intuitive, but the date range syntax in Markwhen is anything but intuitive. Why 2025-01-22 / 2026-10-24? Why not 2025/01/22 - 2026/10/24?
Because this is ISO 8601 date format, the standard date format that intentionally uses dashes to not confuse 25/01/22, 01/22/25 and 22/01/26 which are the same date in different formats (that's why it uses dashes for dates, as for why it uses / for interval I have no idea)
Earlier quoted context omitted.
Because this is ISO 8601 date format, the standard date format that intentionally uses dashes to not confuse 25/01/22, 01/22/25 and 22/01/26 which are the same date in different formats (that's why it uses dashes for dates, as for why it uses / for interval I have no idea)
I know ISO 8601, but that doesn't answer my question. Let me rephrase this, why was a format intuitive to a machine chosen instead of a format which feels more intuitive to a human? I think YYYY/MM/DD - YYYY/MM/DD will mean the correct thing to many more people than YYYY-MM-DD / YYYY-MM-DD, which I suspect many will interpret as an OR and not a RANGE.
Because the “humans” messed up so bad that there weren’t many options left for a simple enough standard.
I would prefer ISO 8601 too over some slight variation which is allegedly more intuitive for homo sapiens sapiens. To keep it simple.
Things like Markdown work because they are intuitive, but the date range syntax in Markwhen is anything but intuitive. Why 2025-01-22 / 2026-10-24? Why not 2025/01/22 - 2026/10/24?
Earlier quoted context omitted.
Hopefully without the latency, it's slow to respond on a 2022 M2 Macbook Air (tried Firefox and Safari)
That's weird. It works perfectly for men much older computers and also on my M2 Mac Pro. What version of OSX are you using? I created that product, btw.
Earlier quoted context omitted.
Because this is ISO 8601 date format, the standard date format that intentionally uses dashes to not confuse 25/01/22, 01/22/25 and 22/01/26 which are the same date in different formats (that's why it uses dashes for dates, as for why it uses / for interval I have no idea)
It's using a slash because that's how ISO 8601 defines time intervals. https://en.wikipedia.org/wiki/ISO_8601#Time_intervals
Note that ISO also permits a double hyphen as the interval separator which is hugely preferable to me personally and also works with file names (as mentioned in that Wikipedia article)
This is really cool, I wish there was some sort of life planner software where I can write down appointments, notes, ideas, and more in a simple format like Markdown, and automatically get notifications/reminders based on what I wrote.