aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorhistoria <gravel.justness270@slmail.me>2024-07-31 03:15:30 -0400
committerhistoria <gravel.justness270@slmail.me>2024-07-31 03:15:30 -0400
commitc4261ee98ef5fd75a208e8e981486ecb4dfcdafc (patch)
tree365841f4fff686a02a8be281157341bb4dc31969 /README.md
parentf60ceeaa79af1e2438b8829c8a32f9187ffb6aa7 (diff)
downloadsoon-c4261ee98ef5fd75a208e8e981486ecb4dfcdafc.tar.gz
Implemented most ranges (missing Julian/Dategroups)
Diffstat (limited to 'README.md')
-rw-r--r--README.md12
1 files changed, 4 insertions, 8 deletions
diff --git a/README.md b/README.md
index c7bd73e..cc742d9 100644
--- a/README.md
+++ b/README.md
@@ -159,9 +159,9 @@ Julian date modulus is definitely weird, but it's a concise way to express multi
Then was created to adapt existing CLI calendars to my personal workflow. Then is not only for the niche of people who use their terminal for scheduling, but for a sub-niche who prefer to edit a file over using a TUI which is why concise, legible syntax is so important. This is a very small group of people who virtually exclusively use [Remind](https://dianne.skoll.ca/projects/remind/). If you're happy with a web or phone calendar, Then probably won't change your mind.
-## Then has concise syntax compared to similar programs
+Then has a few benefits over similar text file calendars:
-It minimizes special characters and simplifies ranges.
+1. **Then has the most concise syntax**. It minimizes special characters and simplifies ranges. Remind is arguably nicer for complex recurring cases and supports more types of conditions, but I rarely need these:
**Then**: `1, Water bill`\
**When**: `* * 1, Water bill`\
@@ -171,19 +171,15 @@ It minimizes special characters and simplifies ranges.
**When**: `m=Jul & d>=1 & d<=7 & y=2025, Vacation!`\
**Remind**: `REM Jul 1 2025 THROUGH Jul 7 2025 MSG Vacation!`
-Remind is wordier but nicer for recurring cases cases that require Julian dates, although I rarely do anything this complex. Remind is inarguably more powerful when it comes to conditions and recurrence:
-
**Then**: `Jul 10-19 2025 J%3-2`\
**When**: `m=jul & d>=10 & d<=19 & y=2024 & !(j%3-2)`\
**Remind**: `REM Jul 10 2025 *3 THROUGH Jul 19 2025`
-## Then *optionally* can archive calendar events.
+2. Then *optionally* can use an archive file to treat events like todos
Take the event "Change air filter", scheduled every 6 months. I might see that upcoming and archive this instance a week early, which removes it from my calendar. Or I might let it slide until next weekend, in which case it sticks around until it's done.
-I use many calendar events (bills, etc.) as a quasi-todo list, so I need to know when I've actually completed them, not just be reminded on a specific day.
-
-## It *optionally* shows a to-do list and upcoming deadlines.
+3. It *optionally* shows a todo list and upcoming deadlines.
# Alternatives