shell question

[Fernando RUIZ CASAS (E-mail)]

> -----Mensaje original-----
> De: cjohns at kiwi.objectivedesign.com.au
> [mailto:cjohns at kiwi.objectivedesign.com.au]En nombre de Chris Johns
> Enviado el: martes, 05 de junio de 2001 0:59
> Para: rtems-users at oarcorp.com
> Asunto: Re: shell question
> 
> 
> Eric Norum wrote:
> > 
> > Does this command interpreter use readline?  If so, command 
> completion
> > wouldn't be hard to add and command-line editing and 
> history is provided
> > automatically.  If not, why not?  I suppose the big problem would be
> > that readline isn't thread-safe :-(
> > 
> 
> Do you have any foot print info about readline on your target ?
> 
The shell.c is low resources consumer. 

I think that readline is useful with disk/floppy/flash history. 
In ram the history is only for the session. 
This can be done easyly but like 'DOSKEY'. 
The second problem is ncurses or similar in order to edit the line.

Curses is a big resources consumer.

Can you think around a system with 512KB ram and several tasks running?

Say me the main use of readline because in shell_readline all is possible.

completion of commands and more is possible.

Let me help you.

> -- 
>  Chris Johns, cjohns @ cybertec.com.au
>