X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: mwoehlke Subject: Re: bash 3.x path completion problems Date: Tue, 30 May 2006 17:53:28 -0500 Lines: 39 Message-ID: References: <83c75fec0605300940s4bb1363s5aa58d8b42e195c3 AT mail DOT gmail DOT com> <83c75fec0605301007n57fbcd80x2e828e10dda436ed AT mail DOT gmail DOT com> <83c75fec0605301033p1fe219a9ve490ce0559a7daf4 AT mail DOT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.2 (X11/20060420) In-Reply-To: <83c75fec0605301033p1fe219a9ve490ce0559a7daf4@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 burning shadow wrote: >> Like I said, it's unlikely that this is the thing that makes the >> difference, but you could >> always have a quick try with the latest snapshot just in case: >> http://cygwin.com/snapshots. It might also be trying the different >> cygwin terminals, xterm >> and rxvt as well as plain old dos console. > > Oh, by the way. I'm working via SSH using PuTTY client. Maybe this is > the case. I'll try snapshots later, thanks. For the record, yes it definitely happens with tab-completion. I've seen a couple of bugs related to prompts with non-printing characters. On a Windows console, my two-line prompt that should end with a bold white '$' loses the bold attribute... but if I do a tab completion that echoes back possibilities, then it is bold unless I try to go back past the beginning of the line, at which point it becomes non-bold. Specifically, the following prompt demonstrates the problem, if anyone wants to experiment: export PS1='\[\e[1;36m\]\w\n\[\e[37m\]\$ \[\e[0m\]' (And yes, it seems to be a bug with the 'set bold' being on the previous line, but it works on all other platforms, for example, if I ssh to a Linux box from the exact same Cygwin window and use the exact same format of prompt, slightly different because I have e.g. \t, \h, etc in it.) On Konsole (from Linux via ssh, with TERM=linux), I see the exact problem you described in the OP. Hitting fixes the cursor so you can see where the *real* end of the line is, but does not erase the junk. Dave, are you saying you can reproduce this in 'stable-latest' but not in snapshots? If so, that's good news. -- Matthew Ncurses. Blessing console programs since 1993. -- 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/