Re: When to use kernel-builtin line editor?

[Edmund GRIMLEY EVANS <edmundo@xxxxxxxx>]

Marcin 'Qrczak' Kowalczyk <qrczak@xxxxxxxxxx>:

> > When does a user have a chance to use kernel-builtin line editor?
> 
> When a program does not use readline or equivalent, e.g. ash (because
> it wants to be small), Oracle (because readline is GPL), nslookup
> (because nobody bothered to implement it).

Or cat, as in "cat > /tmp/file".

> BTW. Is there an alternative to readline? Its interface is *horrible*
> (inconsistency, lots of global variables, abusing C type casts,
> not clear about freeing some memory etc.).

I haven't looked at this at all, but here's a reference. I'd be
interested to hear what you think of it, particularly from a
wide-character point of view:

http://www.cstr.ed.ac.uk/downloads/editline.html :

   Editline is a replacement for the (simple bits of the) FSF readline
   library. It is intended to be useful when readline is too big and/or
   when the readline licencing conditions make it unusable.

   Editline was posted to comp.sources.misc by Rich Salz in August 1992,
   When we needed a replacement for readline because the FSF General
   Public Licence was incompatable with other licences on code used in
   our freely available speech synthesys system, festival

Edmund
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/