X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Chris Croughton Subject: bash filename completion character bug Date: Thu, 20 Jul 2006 05:48:57 +0100 Lines: 35 Message-ID: Reply-To: chris AT keristor DOT net User-Agent: slrn/0.9.7.4 (Linux) X-IsSubscribed: yes 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 Cygwin version 1.5.20-1 (from setup.exe) Bash version 3.1.17(6)-release (--version) (All the latest according to setup.exe) Windows XP Pro SP2 When I do filename completion with TAB I get an extra character on the name: ~$ ba[TAB] BA31INSTALL.LOG basename.exe bash.exe bashdb batt.dll banner.exe basesrv.dll bashbug batmeter.dll ~$ baa This seems to be purely a visual artefact, the actual characters in the input buffer are still correct but all of the editing is then wrong (so doing backspace twice in the above will leave the 'b' visible but not in the input buffer). This occurs on both WinXP-Pro-SP2 machines I use, but not apparently on my Win2k-Pro-SP4 machine (same versions of bash and Cygwin, updated last weekend). I can't see any references to this behaviour on this list or using Google, has anyone else found it? Other programs like bc(1) don't seem to have the problem. (Why am I not using zsh, which doesn't have this problem? Good question: historical reasons, last time I tried it zsh had problems under Cygwin (this was quite a time ago) and I've never got round to changing all my login scripts. And bash is the standard...) Chris C -- 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/