Re: [Bug 1419339] Re: Terminal input offset incorrect after output with no trailing newline and then cycling up through commands

2015-02-11 Thread Anas
Thanks, both those methods work for me. On 11 February 2015 at 00:52, Egmont Koblinger wrote: > Simple version: > export PROMPT_COMMAND='printf "%*s\r\e[K" $COLUMNS' > > More complex version with an inverse exclamation mark: > export PROMPT_COMMAND='printf "\e[7m!\e[0m%*s\r\e[K" $((COLUMNS-1))'

[Bug 1419339] Re: Terminal input offset incorrect after output with no trailing newline and then cycling up through commands

2015-02-10 Thread Egmont Koblinger
Simple version: export PROMPT_COMMAND='printf "%*s\r\e[K" $COLUMNS' More complex version with an inverse exclamation mark: export PROMPT_COMMAND='printf "\e[7m!\e[0m%*s\r\e[K" $((COLUMNS-1))' -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscrib

[Bug 1419339] Re: Terminal input offset incorrect after output with no trailing newline and then cycling up through commands

2015-02-10 Thread Egmont Koblinger
This is not a gnome-terminal bug, you'll see the same behavior in every terminal. The problem is that there's no reliable way of querying where the cursor is, so bash assumes it's in the 1st column when it prints the prompt and edits the command line. If it's not there, screen corruption is bound