This is the mail archive of the
mailing list for the Cygwin project.
Re: bash kills console history
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Sam Steingold <sds at gnu dot org>
- Cc: cygwin at cygwin dot com
- Date: Fri, 20 Jun 2003 18:41:05 -0400 (EDT)
- Subject: Re: bash kills console history
- Reply-to: cygwin at cygwin dot com
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 <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>.
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).
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.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