> Eric, > > Not sure if you are the person to address this to...but since you appear > to be the Cygwin maintainer for Bash, I figured I'd throw it your way.
http://cygwin.com/acronyms/#PPIOSPE $ tail -n 1 /usr/share/doc/cygwin/bash-3.0.README Please address all questions to the Cygwin mailing list at <cygwin@cygwin.com> > > Since the upgrade to 3.0-7, I've seen all sorts of quirky stuff > happening with the prompt -- things that worked fine with 2.x. For some > reason, the presence of escape sequences seem to leave the terminal > prompt in a strange state where cursor/line positioning seems to get off > track: > > PS1='\[\e]0;termwindow\a\][plaintext]> ' Known issue. See http://sources.redhat.com/ml/cygwin/2005-07/msg00259.html. I'm looking for time to try and find a fix. > > On my machine, the prompt has two spaces after the '>' character (it > should have only one). Now to see the quirky behavior, try > tab-expanding any command (like ps). As soon as you type 'ps[TAB]', the > cursor will move to the correct location. But the weirdness does not > end there. If you just let the character repeat on any key take you > near the end of the line in the terminal, it will return with a linefeed > before it gets to the end. If you want to see an exaggeration of the > problem, try this prompt: > > > PS1='\[\e]0;[EMAIL PROTECTED]:[EMAIL PROTECTED]:\[\e[3 > 4m\]\w\[\e[0m\]]> ' > > Things look normal with that one until you try the tab expansion thingy > again. Type 'ps[TAB]' produces something that looks like this: > > [EMAIL PROTECTED]:~]> ps]> ps > > I've tried these prompts on a few other platforms running versions of > Bash 3.0.x. On a Solaris machine, I compiled the latest bash source > tarball after applying all of the patches I could find -- GNU bash, > version 3.00.15(1)-release (sparc-sun-solaris2.8). No problems with > that one. I also tried it on a recent Linux distro -- GNU bash, version > 3.00.16(2)-release -- and didn't encounter any issues with that one > either. Just to be sure that it wasn't something unique to the one > machine, I also tried it on another cygwin installation on another > machine, and it had the same problems. > > I know it's not critical, but it certainly can be annoying when > characters begin to overwrite each other during tab expansions (of which > I tend to overuse). At any rate, I hope it helps you sort out any bugs. > > Thanks, > Rob > > > -- > Rob Gillen > Inovis, Inc. -- Eric Blake volunteer cygwin bash maintainer -- 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/
