Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Fri, 20 Jun 2003 18:41:05 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Sam Steingold cc: cygwin AT cygwin DOT com Subject: Re: bash kills console history In-Reply-To: Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 20 Jun 2003, Sam Steingold wrote: > when I start a non-cygwin interactive application in a console window > under cmd, I can recall the previous lines with the key and edit > the current command line with and . > when I start the same application under bash, I can no longer recall > history with (although & 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 . > > Thanks! Sam, Does the interactive application check whether its output is a console? If it does, and bash uses a pty (which is a pipe, not a console), then the application may decide that it's not running interactively (disabling the history mechanism). When gdb runs the application, it allocates a separate console for it, so you get interactivity. If my guess above is correct, there is no way to fix this short of always opening the application in its own console (or fixing the application code, if it's available). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/