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
To:	cygwin AT cygwin DOT com
From:	"ImranKhan" <imran_k01 AT hotmail DOT com>
Subject:	Re: Bash Command History Scroll Back Problem with Multi-line Commands
Date:	Thu, 23 Jun 2005 14:59:05 -0400
Lines:	30
Message-ID:	<d9f0dr$23e$1@sea.gmane.org>
References:	<d9etbf$oeh$2 AT sea DOT gmane DOT org> <42BB0603 DOT 20745D88 AT dessent DOT net>
X-RFC2646:	Format=Flowed; Original
X-IsSubscribed:	yes

Yup, thanks guys, I found out the exact source is the prompt setting:

This does not work:  export PS1="\e[32m\w$\e[0m "
This works fine:   export PS1="\w$ "

I inherited this bashrc, so the first settings are hieroglyphics to me. 
Seeing as I don't care much about colour anyway, I'll just remove it.


Thanks so much!



"Brian Dessent" <brian AT dessent DOT net> wrote in message 
news:42BB0603 DOT 20745D88 AT dessent DOT net...
> ImranKhan wrote:
>
>> 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?
>
> No problem at all here.  This is usually caused by improper use (or lack
> of) \[ and \] in the prompt to tell bash which characters are
> nonprinting.
>
> Brian
> 




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