I may be mis-understanding your question, but you have to be sure history is enabled on bash and you have HISTFILE set.
CMD.EXE is a different shell with different history semantics. Under bash, I set 'vi' to 'on' to get get 'vi' compatible editing, but up/down arrow still work. You also have to be sure that you have history turned on. "man bash" explains alot of the options you will find under "set -o". Oh -- another thing -- the history that BASH keeps is / will be a separate history from the history kept by CMD.EXE. So if you don't have a HISTFILE defined that stored commands from your last BASH session, then starting BASH fresh would start with no history -- the commands that were typed into CMD.EXE are in CMD's private history stash. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sam Steingold > Sent: Fri, Jun 20, 2003 2:11p > To: [EMAIL PROTECTED] > Subject: bash kills console history > > > when I start a non-cygwin interactive application in a console window > under cmd, I can recall the previous lines with the <Up> key and edit > the current command line with <Left> and <Right>. > when I start the same application under bash, I can no longer recall > history with <Up> (although <Left>&<Right> still work). > > What does bash do to disable it? > How can I get back history editing? > > Note that when I run the same program under GDB (which runs under > bash!) I do get to edit previous commands with <Up>. > > Thanks! > > -- > Sam Steingold (http://www.podval.org/~sds) running RedHat9 GNU/Linux > <http://www.camera.org> <http://www.iris.org.il> > <http://www.memri.org/> > <http://www.mideasttruth.com/> > <http://www.palestine-central.com/links.html> Life is like a diaper -- short and loaded. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/