[Extremely Minor Inconsistency] Sorting and colors in command user are inconsistent
yba3ro
<user deleted>
{210205.2055}
When you use the `0user` command alone, you'll get an output something like this.
`1>>``0user`
Usage: `0user` `V<username>`
Your users: `0a`, `0b`, `0c` (3 / 3) `l// usernames sorted alphabetically, vlan users shown with darker gray`
Retired users: `0d` (1 / 5)
Active user: `0a`
But when you use something like `0user` `1asd` while having all of your user slots occupied, it prints this:
`1>>``0user` `1asd`
>>user asd
<color=#FF0000FF>3 of 3 available users created. </color> `l// note broken coloring`
Use `0store_list` to purchase more slots.
Your users: `0c`, `0b`, `0a` `l// usernames sorted by creation date, ascending, vlan users shown with same color as other users`
When you try to claim an unavailable user, yet another scenario occurs:
`1>>``0user` `1x`
<color=#FF0000FF>User x is unavailable.</color> `l// note broken coloring`
Your users: `0a`, `0b`, `0c` (3 / 3) `l// usernames sorted alphabetically, vlan users shown with darker gray`
Retired users: `0d` (1 / 5)
It'd be nice if these were more consistent.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
dtr
{210215.0240}
Honestly I like the sort inconsistency. Or rather: alphabetic is nice to have most of the time, but creation-order is *too* (and we can't always use users.inspect for that -- vlan users, for example). SO as much as I'd prefer consistency, I don't want to lose the ability to see users in creation order.
( the broken coloring should be fixed tho! )
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -