You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realized that adjusting volume is now done this way
socos volume {ip} -30
that feels a bit backward, wouldn't it make more sense to reorder it to:
socos {ip} volume -30
or do this a bit smarter, by not requiring a specific order. We have a list of valid commands, so we can search for one of those within the list of parameters, and we can search for valid arguments to these commands, this way we would recognise that:
socos {ip} volume -30
is actually the same as e.g.
socos volume -30 {ip}
Another command that ends up this way is:
socos play {ip} 20
The text was updated successfully, but these errors were encountered:
petteraas
changed the title
Ordering of paramerters when not opening interactive shell
Ordering of parameters in cli mode
Apr 12, 2014
I agree that the original order seems a bit backwards. I'm not sure if it is worth the trouble though to remove the dependence on the order, since that might make the checks of "valid arguments" quite tricky. I think the socos {ip} command any number of command args syntax is good and simple (to use and implement).
I realized that adjusting volume is now done this way
that feels a bit backward, wouldn't it make more sense to reorder it to:
or do this a bit smarter, by not requiring a specific order. We have a list of valid commands, so we can search for one of those within the list of parameters, and we can search for valid arguments to these commands, this way we would recognise that:
is actually the same as e.g.
Another command that ends up this way is:
The text was updated successfully, but these errors were encountered: