The CLI *(term) is an *(acronym) for Command Line Interface, a kind of *(user interface).

CLIs use a simple _(paradigm) of issuing commands to the system using words (They are one kind of a _(TUI)). CLIs are very efficient, but their commands are rarely _(visible). A CLI with good, consistent names and thorough documentation would be somewhat easy to learn, and fast.

The classic example is the _(Unix) command line. This typically operates under a shell (e.g. bash, ksh, and the author's favorite, zsh) which is a simple but almost always _(turing|turing machine) equivalent language. Unfortunately, the _(Unix) naming convention is something along the lines of "if the name is understandable, relevant to whatever it represents, or consistent in any way with the rest of the system, rename it", making using the _(Unix) command line hell to the uninitiated. Otherwise it is very efficient.

<UL CLASS="links">
  <LI>_("CLIsource: A resource for the command line interface"
  | http://polylithic.net/cli/)</li>
</ul>

<HR>
The big problem with CLIs is the shortage or, sometimes, total absence of feedback. A better _(paradigm), which subsume _(CLI)s, are _(TUI)s. -- _(Mad70)
