Set duration for tasks or blocks

[clshafer]

Is it possible to set a start and end time for a task or event? This would better support time blocking.

[Quorafind]

A duration is good, but need some good design for not adding too much mark to text.

[insecurejezza]

Here are some options you could use. You could use the syntax HH:mm - HH:mm to mark start and end time.

the Day Planner plugin manages end time by making it one minute before the next task starts. Then there is a dedicated end task block to mark when the day is finished.

[Quorafind]

@insecurejezza Maybe an option to select will be good, 🧐 Will be available in next release.

[clshafer]

I like the idea of the end time being optional. If none is provided system defaults to a value that might be set by the user in the options. If an end time is provided system takes that.

[ms3056]

How about making the assumption that the duration of an entry is the start time up to the next event?

09:00 Morning Routine 10:00 Meeting with Bob 11:00 Lunch

This would be :

09:00-10:00 - Morning Routine 10:00-11:00 - Meeting with Bob

I would also like to see the text in the Day calendar view.

[bramses]

I think the format {start - end} would be great!

[lee-b]

There is a standard for ranges in normal english grammar: the en dash (not to be confused with the em dash).

There is also a common/de facto pseudo-standard for rendering that as pure ASCII/typewriting: double minus (--). Technically there should be no spaces around a real en dash (a--b, not a -- b), but adding spaces is common for ASCII. Again, not to be confused with the em dash --- which is for marking parentheses/delays. That would normally be written as --- in ASCII/typewriters.

Would suggest that all times of the format HH:mm[\s+]--[\s+]HH:mm be recognised as events/meetings with absolute start and end times.

For relative end times (start +30m), the symmetrical if not immediately intuitive markup could be ++, as in HH:mm ++HH:mm and ++30m.