It also changes the keys sorting to display the numeric namespaces first.

Why not just stick to fixing the bug? It's not strictly a bug that numeric entries come before or after alphabet entries; that's a personal preference and probably breaks someone's workflow.

This bug proves that numeric namespaces were not taken into account when the code was written. Therefore it's a good occasion to improve their support in addition to purely fixing it.

Displaying the numeric namespaces first is a change that makes sense to me, not because it's a personal preference but because comparing items as strings with theSORT_STRING flag seems the best option since we are displaying strings. Turns out numerics come before letters with this flag...

I doubt this is going to break someone workflow since numeric namespaces are currently not displayed correctly at all (except 0). By fixing the bug, we are already changing the output anyway. Also, I doubt we have a BC break policy on commands output.

Of course, this change is a proposition that I will gladly revert if it is considered useless / bad / not backward compatible by a majority.

I doubt this is going to break someone workflow

I was trying not to make this about me, but the implication was that it breaksmy workflow. I like my custom commands to appear at the end of the list so they don't always scroll off the top of the terminal when listing commands. Using numeric namespaces currently accomplishes this, but with your proposed change, one would have to rename everything to begin withz or some other late-sorted character to achieve the same result.

Could you please add a test case?

I added a test. There is one edge case we don't support: when you have "0" as the command namespace, its sorted order depends of its processing order. Seehttps://3v4l.org/SJcMB.

Thank you@fancyweb.