delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/06/20/20:02:53

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "linda w \(cyg\)" <cygwin AT tlinx DOT org>
To: <cygwin AT cygwin DOT com>
Subject: RE: bash kills console history
Date: Fri, 20 Jun 2003 17:02:28 -0700
Message-ID: <000301c33788$673e6c50$1403a8c0@sc.tlinx.org>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <ud6h8mp34.fsf@gnu.org>

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: cygwin-owner AT cygwin DOT com
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Sam Steingold
> Sent: Fri, Jun 20, 2003 2:11p
> To: cygwin AT cygwin DOT com
> 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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019