Command recall that is used in all Leaf variants uses a patch made by someone from the LRP community to add 'command history' to the original ASH.
It may be possible that this patch is not functional for long lines. Please note that ash has had no changes since 1999... -----Original Message----- From: Simon Blake [mailto:[EMAIL PROTECTED]] Sent: Sunday, October 13, 2002 9:07 AM To: Nathan Angelacos Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [leaf-devel] Command recall Oxygen(yes) Bering(no) DF(no) I've certainly noticed commandline recall problems with Bering - uneditable multilines, and also weird behaviour with the history buffer appears to get corrupted and adds crap to the end of some commands in the buffer. So you're not alone :-) Cheers Si On Sat, Oct 12, 2002 at 03:38:34PM +0000, Nathan Angelacos said: > > It pains me to realize that I've been using command > > recall in Ox, DF, and BF for a long time now. The > > up arrow works great. My apologies for losing my mind. > > Perhaps you aren't losing your mind... > Do you also have the experience that that ash seems > to have problems with the "up-arrow" command recall > when the command is greater than the screen width - > you can't edit the first part of a multiline > command? (where multiline is a long command line > without the use of '\' ?) > > > Thanks for the explanation. I guess what I'm really > > missing in filename/directoryname completion. > > After checking further, BusyBox ash (0.60.3) with > command auto completion seems to work here on bering > if you: > > compile EXPR into busybox, and comment out line 204 > in linuxrc: > # expr () { exp $@ ; } > > Probably you could get away with not compiling in > expr and changing line 204 to read: > expr () { $(( $@ ; )) } > > But the shell gurus should comment on that theory... > > > Also, at the top of linuxrc (line 30 something) there's > a call to [, which fails since busybox hasn't been > installed yet. Guess its a shell internal in ash, but > a "program" in BB. > > The offending line is: > > if [ $DEBUG ] ; then > > A solution might be to change the line to read: > if /bin/busybox test $DEBUG ; then > > > or just define BB=/bin/busybox a little earlier in > the script and then call > if $BB test $DEBUG ; then > > That seems to run through the linuxrc without any > errors, and gives a nice shell with auto completion > and correct behavior in using command recall. > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > > _______________________________________________ > leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
