Feature: Support for multiple levels of headings

[MacDefender]

It would be great to have have multi level support like:

Tasks

Tasks for Nix

Update

Tasks for Brew

Update

When such a file is used xc first asks if you want the Nix or Brew section and after that shows again a selection for just the tasks below that heading. For non-interactive maybe multiple tags like xc nix update would be great. This would allow shorter selection menus and having just one file for all tasks on a system.

This would also allow to have different hosts supported as one could first select a host heading and after that the task selection with host specific modifications. Maybe even more that just 2 levels and support for ENV vars like XC_HEADING_1 = myHost to auto select a sub heading without asking for it.

[a-h]

I like this idea.

I have started to get very long lists of tasks for bigger projects, when actually, they could be better done as README.md files done in subdirectories.

If the menu also allowed you to traverse down to README.md files in subdirectories, that would be excellent.

[joerdav]

Interesting, I like the idea. Seems valuable.

Myself, I've been using collapsing elements when a README gets too big (see below), which works because xc is super dumb :D. I can see why this would be valuable though for more structured task lists.

---

Hide all commands:

Tasks

Useful commands for this codebase

Task1

echo Task1

Task2

echo Task2

---

Or just hide commands that aren't used often:

Tasks

Task1

echo Task1

Other commands

Task2

echo Task2