Hi,

I confim bizoo’s post too.

I understand there are two opposite trends on Build System: show just the items for the selected one, have access to all Build System without selection.

Very likely we don’t need to have access to ALL of them, but just more than one…

It’s something that happens in our projects: we have some common tasks to run along with specific actions depending on the compiler family.

Now we replicate the common tasks in 2 Build Systems.

My proposal

-> Allow the selection of multiple Build Systems

Then the entire list would be just the merging of the items coming from the enabled Build Systems.

In this way we can fall back on the current implementation, just one selected.

But we can extend it to show up an enriched list to cover 2 or all available Build Systems.

I would recommend an “enable/disable all” “toggle selection” actions on the Build System list, so that most of the combinations are achievable in few clicks…(even though I rarely abandon the keyboard and love ST for letting me doing that)

I left to you details on how “ctrl+b” & sons should work.

Does it sound inline with ST philosophy of having multiple stuff, doesn’t it?