Ability to view tasks from all lists

[berkes]

In addition to #36, I'd love to have a way to list all tasks from all lists.

E.g. When no --tasklist is provided, it will loop over all taskslists and for each one list the tasks.

With some shell scripting, I can do this, but it's not very clean:

for list in $(gtasks tasklists view | cut -c5-); do
   gtasks tasks view --tasklist $list
done

This does not allow for sorting, filtering etc. With qsv, I would manage.

The output could include a column "Tasklist" so that we can sort/filter/etc on that too.
Sorting should probably work over all taskslists.

[BRO3886]

Thanks for the suggestion! This is a reasonable feature request, but it now conflicts with the default task list behavior added in #51.

Currently, when no --tasklist is provided, the resolution order is:

1. -l / --tasklist flag
2. GTASKS_DEFAULT_TASKLIST env var or default_task_list in config file
3. Auto-select if only one list exists
4. Interactive prompt to pick a list

Implementing "no tasklist = aggregate all lists" would break step 3 and 4 for users who rely on the prompt or the single-list auto-select. It would also be surprising behavior for users who haven't set a default — running gtasks tasks view and getting every task across all lists is a lot of output with no warning.

A possible path forward that doesn't break existing behavior: add an explicit --all / -a flag to tasks view that aggregates across all lists, with an optional Tasklist column in the output. That way the default path stays predictable and users who want the aggregate view opt in explicitly.

Open to feedback on this approach.

[berkes]

Thanks for the speedy reply. I was indeed aware of #51, but hoped this feature request may come in time to help shape that other one. No prob though.

Thinking of alternatives, I see:

• --tasklist attribute can be repeated, e.g. --tasklist home --tasklist errands --tasklist inbox would merge these.
• --tasklist attribute can be a list. Same as above, but instead of repeating arg, one can provide a comma separated list; e.g. --tasklist home,errands,inbox.
• --tasklist all, special value to list all. all would give problems if people have a tasklist called "all". Maybe [all], or "*" or ALL or such? "any", or other words may work too.
• --all as you mention, downside is that this makes mutually exclusive arguments (all OR tasklist, never both) which, in my experience, is rather confusing and difficult to implement in many common optparse libs.

For my cases, the repetition would work "good enough". As I don't change the tasklists that often, so hardcoding them in some aliases in my shell is fine for me.