Re: still having cursor problems on MacOSX Terminal and iTerm

2006-12-22 Thread Chet Ramey
[EMAIL PROTECTED] wrote: > I have it set thusly now: > PS1='\[\e[0;7m\]\h[\w]\n\u\$\[\e[0m\] ' > . ^^ two-line prompt > Is \n considered a printing character or not? Yes. It causes the visual display to change: the cursor moves to the next line. Readline takes the newline

Re: still having cursor problems on MacOSX Terminal and iTerm

2006-12-22 Thread sci-fi
On 2006-12-22 08:40:21 -0600, dearvoid <[EMAIL PROTECTED]> said: On 12/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On 2006-12-22 04:34:22 -0600, dearvoid <[EMAIL PROTECTED]> said: I will need to "close" each prompt line with an end-hilight code, do the \n, then begin the next line wit

Re: still having cursor problems on MacOSX Terminal and iTerm

2006-12-22 Thread dearvoid
On 12/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: On 2006-12-22 04:34:22 -0600, dearvoid <[EMAIL PROTECTED]> said: I will need to "close" each prompt line with an end-hilight code, do the \n, then begin the next line with a start-hilight code, such as: PS1='\[\e[0;7m\]\h[\w]\[\e[0m\]\n\

Re: still having cursor problems on MacOSX Terminal and iTerm

2006-12-22 Thread dearvoid
On 12/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I've seen visual glitches like this for so long, I think they might be more to do with Apple than with GNU-&-company. I've applied all nine official patches thus-far to bash-3.2 and the one official patch to readline-5.2, have pointed t