Systemctl does option-command not command-option?

1 points by AtlasBarfed ↗ HN
I don't know if systemctl is fundamentally better under the hood, but the CLI is mystifying. You can't autocomplete a verb on the command line without the noun for context, or to put it another way, you can't autocomplete the options for a command if you don't have the command already specified for context.

So if I do systemctl <checkstatus> <myservice>

the command line can't autocomplete the verb/option "checkstatus" since it has no idea what service (the noun/command) I'm doing.

What is the possible justification for systemctl <option> <command>? In terms of very very basic CLI culture, even for complex CLI commands with subcommands it is always <command> <subcommand> <options/args>.

And it's basically too late to fix it.

0 comments

[ 2.9 ms ] story [ 12.4 ms ] thread

No comments yet.