This can take a few forms. The easiest is to add them to the detailed helptext for the appropriate command, but this can take one of two forms:
List at the bottom of the helptext any and all aliases (section "Aliases", bulleted list under it)
Put in parens at the end of the title one alias. Designate in config which alias is the primary alias to print here ({..."primary": true,...}). If more than one alias is primary, use the first one we see because this is a silly config anyway.
Alternatively, we could separate it a little more and add an aliases command (Cadence aliases), which autogenerates a list of aliases for that command (Cadence aliases play => "Cadence play has the following aliases: ...", or Cadence aliases stop => "Cadence stop has no aliases" - Or some such)
This can take a few forms. The easiest is to add them to the detailed helptext for the appropriate command, but this can take one of two forms:
{..."primary": true,...}
). If more than one alias is primary, use the first one we see because this is a silly config anyway.Alternatively, we could separate it a little more and add an
aliases
command (Cadence aliases
), which autogenerates a list of aliases for that command (Cadence aliases play
=> "Cadence play has the following aliases: ...", orCadence aliases stop
=> "Cadence stop has no aliases" - Or some such)What is best is an open question.