On 2025-08-09 18:04, Remind list wrote:
> On Sat, 9 Aug 2025 11:54:23 -0500
> Tim Chase via Remind-fans <[email protected]> wrote:
> > My gut feeling is that it mostly just mimics existing functionality,
> > and fails to be as flexible as existing functionality.
>
> OK, fair.  I also don't use tasks or TODOs (the joy of being retired!)

Hah, my todo list is largely quotidian household stuff, not
work-related.  While not *retired*, I've been a SAHD and have managed to
limit the number of hours I contract out, so it's _almost_ like being
retired while still staying out of trouble ;-)

> Even the ICAL standard distinguishes between events (VEVENT) and tasks
> (VTODO).  Right now, there's no decent way to convert an ical VTODO to
> anything in Remind.

Maybe this is a different type...we have MSG, MSF, CAL, PS, PSFILE,
SATISFY, and SPECIAL, so it might make sense to have a TODO type too,
something like:

  REM Thur TODO Take out trash

> 1) Possibility to convert more faithfully to and from ical format.
>
> 2) Possibility for front-ends such as TkRemind and Wyrd to offer a
> Task view with all the conveniences users might expect (easily mark a
> task done, for example.)

By making a new type for it, you can hopefully (re)use all the existing
infrastructure for recurrance and times, while also allowing for
filtering just TODO events for converting to/from iCal, and also allow
the GUI/TUI front-ends to handle TODO entries specially if desired.

It also would summon the rule that expression-pasting can't change the
type of an event:

  You cannot use expression-pasting to determine the type (MSG, CAL,
  etc.) of a REM command

So nothing like

  REM Thur [iif(random() % 2 == 0, "MSG", "TODO")] Surprise!

which might cause unfortuante behavior.  So I like that aspect, too.

Just more random brain dribblings :-)

-tim
-- 





_______________________________________________
Remind-fans mailing list
[email protected]
https://dianne.skoll.ca/mailman/listinfo/remind-fans
Remind is at https://dianne.skoll.ca/projects/remind/

Reply via email to