Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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:	ericblake AT comcast DOT net (Eric Blake)
To:	ImranKhan <imran_k01 AT hotmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Bash Command History Scroll Back Problem with Multi-line Commands
Date:	Thu, 23 Jun 2005 18:42:12 +0000
Message-Id:	<062320051842.17766.42BB02840008F1000000456622007510900A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender:	ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> This falls in the annoyance category.  Anyone have problems using scroll
> back history with commands that are long and split over muliple lines in the
> terminal?
> 
> What happens is that the screen doesn't get refreshed properly and the
> cursor seems to placed in the wrong spot..

Please report more information:

> Problem reports:       http://cygwin.com/problems.html

Are you using bash-2.05b-17 or bash-3.0-2?  If you are using the older one, try the experimental new version to see if it was an upstream bug that has already been fixed by the new release.  Which terminal are you using (Windows, rxvt, or xterm)?  Also, report what "echo $TERM $PS1" shows - I know that if you tell bash the wrong information as to which characters in the prompt are actually printing characters, bash is bound to be confused.  Also, the style of history completion can be controlled by various shell options, so report the output of "shopt | grep hist" and "env | grep HIST".

--
Eric Blake
cygwin bash maintainer



--
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 -