Feature Request

Not a feature not a bug, just an enhancement:

Is your feature request related to a problem? Please describe.

Currently, the cmd_duration module does not render time components which equal 0, meaning that the format is inconsistent in its length when multiple components are involved, making it hard to know what I am looking at at a glance:

• 7260 seconds will render as 2h1m
• 7201 seconds will render as 2h1s
• 7261 seconds will render as 2h1m1s

Describe the solution you'd like

• Render all components after the first non-zero component even if they are zero, so the examples above would become to make them scannable at a glance:
  • 7260 seconds would render as 2h1m0s
  • 7201 seconds would render as 2h0m1s
  • 7261 seconds would render as 2h1m1s

Describe alternatives you've considered

• Always reduce the output to the two (?) highest components to make it consistent but compact without loosing too much significant information. Probably viable but would kind of break the show_milliseconds config
  • 7290 seconds would render as 2h1m
  • 90100 seconds would render as 1d1h
• Leave it as it is. Has the advantage of being no change and no work, but the disadvantage of being inconsistent to scan for no real gain

I would be happy to implement this