Hello, on Saturday 29 October 2011 at 10:32, Nicholas Marriott wrote: > What exactly is in your prompt? > > Either send it through cat -v or run script and hit enter a few times > then send me the script file.
It turns out that my prompt is generated by a callback, so `cat -v` is not an option. I attached prompt-bright.script exhibiting the problem (or rather, that would exhibit the problem if there was text entered), while prompt-ok.script shows a variation that is fine *except* on the first line (since `script` starts with a clean state, I had to use the first line to trigger the error reported as the bold "1" which reverts colors to the non-bright correct state). This is exactly how I got the two different versions on the screenshot. > It is clearly your prompt that is causing tmux to leave bright turned on > until the SGR 27 you send causes it to reset. I bet clearing any attribute > will do it, not just reverse, because they will all trigger an SGR 0. Yes, the prompt is indeed causing that, but the last part of the printf'ed lines in the screenshot shows that "\033[36m whatever \033[m" *also* triggers the problem where bright stays turned on, and I bet this sequence is much easier to analyze than my prompt. Thanks for your help, Natacha Porté
prompt-bright.script
Description: Binary data
prompt-ok.script
Description: Binary data
------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
