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
Date: Tue, 23 Aug 2005 09:07:47 -0700
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: bash prompt problem - some more observations
Message-ID: <20050823160747.GD3156@efn.org>
References: <3333F09C50966C499FD3A3E8FA4514C2334E86 AT sydexchange1 DOT vignette DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3333F09C50966C499FD3A3E8FA4514C2334E86@sydexchange1.vignette.com>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes

On Tue, Aug 23, 2005 at 05:45:42PM +1000, Robinson, Mark wrote:
> howdy
> 
> so I downloaded the cygwin bash source and built it without multibyte
> character support and guess what?  no bug.

And if you build your own bash *with* multibyte character support, you
*do* see the bug?

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