2 ms·
Because you need a lot of work to make command-line session to be as good as CLI. Especially my CLI which I have customized just the way I like. To take fdisk
by theamk 5y ago
Because you need a lot of work to make command-line session to be as good as CLI. Especially my CLI which I have customized just the way I like.
To take fdisk for example: I hate it and try to avoid it as much as possible. For example, after fdisk session, I have no record of the commands I executed in my history file. Copying the command to put into wiki is pretty hard. And I cannot type $((128 * 1024 * 1024)) in place of the argument. And if I want to execute the same sequence of operations multiple times on a different disks, there is no way to do so.
If you want to make a complex command more discoverable, start from a shell completion rule, or a good manual. Don’t bother with interactive session unless you are sure you can make it better than an existing shell.
- fouc 5y agoThat's a good point about the lack of history & difficulty of sharing the commands. Perhaps there's a middle ground between the shell & fdisk, where they can meet in the middle and produce the same interface, but maintain all the advantages of the shell history and parsing.