command line history not saved

[braindrop]

i thought this would be an easy one but after searching for awhile i havent found an answer.  on my 5500 with oz 3.3.5, i am trying to get the konsole to save the command history.  so far i have set the HISTFILESIZE to 50 as well as the HISTSIZE.  i have a file called .ash_history that i can manually put lines into and they will be read when i start the konsole but it does write the lines on its own like it should. what am i doing wrong€

[braindrop]

how about this, can i setup my profile to echo all the commands i type to a file as well as the screen?

[superbondbond]

Hey braindrop, I saw your thread about this over at LQ.

Not sure if this will help or not, but I have noticed that if I close out the console by tapping the \"x\" in the corner, it doesn\'t save the bash history. But if I close it out by typing \"exit\", it does.

(I\'m running OZ3.2 on a 5500)

[braindrop]

oh wow. thanks.

[herbivore]

OK, so my zaurus was all cool, I didn't upgrade for a long time, now I switched to oz 3.5.3 from 3.2 ( I think).  I am having problems with saving the history again.  I tried all the stuff from this thread, and also I tried the 'save history' from the connection tab on console.  I can't get the history to save, can someone help me out?  I don't know if it is a local configuration problem or other problem, but when I type exit, it just stops activity on that tab, it doesn't actually close the tab.

I tried making the files in /home/root/.ash_history, and /home/root/.history, and then adding some commands to them, but it doesn't sem to read them either.

[herbivore]

So am I asking a dumb question, or does everybody really not have a comand line history?  About 80% of what I do is on the command line, this is frustrating.

[lardman]

I have history but only for a single terminal session.

Is this a limitation of the busybox sh?


Si

[herbivore]

From what I have read on the busybox site, it appears to be.  With the old 3.2 setup though, typing exit to leave the console would append the current sessions history to a history file, now it does not.  I guess this may have been a feature of console, and not sh?

[herbivore]

OK, from a little poking around on the busybox site, it appears that the default for the shell is to be compiled without history, or command line editing support, or fancy prompts, etc, but it does have all that potential.

So now my next question is, do I have to recompile the whole busybox to fix this?  Would any problems be expected from trying to replace the current busybox that is installed?  

The information I am looking at is the config files and such for the shell at this page:  http://www.busybox.net/cgi-bin/viewcvs.cgi.../busybox/shell/