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-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Luciano Subject: Re: first line overwritten in Bash Date: Sat, 12 Apr 2003 01:22:19 +0000 (UTC) Lines: 18 Message-ID: References: <5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030411175636 DOT 0261b920 AT pop3 DOT cris DOT com> X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Xnews/5.03.24 I see. Your suggestion works, but it's clear that I have to read (even) more documentation. That thing is huuuge... Thanks. Luciano ES Santos, SP - Brasil ******************************** Randall R Schulz wrote in news:5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030411175636 DOT 0261b920 AT pop3 DOT cris DOT com: > You're not signalling BASH (and the readline library it uses) > which portions of that prompt do not produce characters on the > screen. That causes it to lose track of where the cursor really > is when the prompt is printed. Any non-printing sequence in PS1 > should be surrounded by \[ and \]. See the PROMPTING section of > the BASH manual for more details. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/