Jukka Salmi wrote: [Wed Apr 08 2009, 07:04:38PM EDT] > BTW, I'm using a two line prompt > > $ set | grep ^PS1 > PS1='\...@\h:\w [\t]\n\$ '
Me too. My prompt is significantly more complex, though. It involves computation prior to display. See http://agriffis.n01se.net/skel.hg/index.cgi/file/tip/bashrc.prompt The end result, in most cases, is a two-line prompt with a bar that spans the width of the terminal. For example, $ printf '%q\n' "$PS1" $'\\[\E[0m\E[32m\\]--- \\[\E[0m\E[01m\E[32m\\]0 \\[\e[0m\e[32m\\]agrif...@oliva \\[\E[0m\E[34m\\]~ \\[\E[0m\E[32m\\]-------------------------------------------------------------------------------------------------------------------------------------\\[\E[0m\\]\n\\[\E[0m\E[32m\\]$\\[\E[0m\\] ' > and noticed that sometimes when I start a new urxvt(c) the prompt is not > printed correctly: everything up to the newline is fine, but then the > newline and the \$ are not output, and the cursor shows up in the second > to last column of the same line; a Ctrl-L restores the prompt to normal. I have the same problem, and like you, I think it's a race condition because it only happens some of the time. I see it with both bash-3 and bash-4. Aron _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
