|
|
|
|
|
|
by WhitneyLand
2743 days ago
|
|
|
Hasn’t anyone tried to add some kind of interactivity to command line typing to eliminate this advantage? Not something simplistic like keyword completion, more like the best state of the art code editors or ides. In those environments its just text based still, but can be incredibly rich and efficient. You can get seamless acesss to info on any language command or param, predictive code completion suggestions, based on machine learning, easily refactor/correct parts of a line you’ve already started typing, etc. The thing is it doesn’t have to get in the way if designed right. So someone can also just sit down and blaze away typing and ignore it. |
|
|
One example: /bin/rm has the -i (for interactive option). Some people alias 'rm' (or if they are newbs, it is sometimes aliased for them by someone senior in their org) to 'rm -i', which helps avoid deleting files by mistake, due to typos or typing too fast. With -i, rm asks for confirmation before deleting each file. This is more important in Unixes because most of them do not have any undelete utility; nor does Windows, AFAIK, except for 3rd-party ones like the Norton Utilities (does it still exist?), which need to be installed. And installing the utility (if you can get it) after an accidental delete, has some chance of the utility getting installed onto disk blocks earlier occupied by the deleted file.