Indeed, given applications are not good examples for this matter.
Although it would be somewhat a waste of bandwidth, but having a
screenshot of a CLI application with output its produces for a typical
use case sounds like a good idea IMHO.
Or, to make it less waste, I suggest to allow for a 'screenshot' to be
of .txt format, where CLI applications would have a terminal output from
a few typical use cases outputs. IMHO those would be quite useful to
assess the interest of a user to a given package.
On Fri, 05 Jan 2007, The Fungi wrote:
> On Fri, Jan 05, 2007 at 03:47:56PM +0100, Javier Fernández-Sanguino Peña
> wrote:
> [...]
> > There is some cli software (links, mutt and mp3blaster come to mind)
> > that have nice text-based UIs
> [...]
> To get pedantic, the applications you mention do have text-based
> interfaces, but are not good examples of a command-line interface
> (bc, sed, ed, ps, ls, cat...). Note the package descriptions for
> your examples say text-based, character mode, console, et cetera;
> but none mention their command-line interface (for those that even
> have one).
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
