You are not logged in.
In the left term in this scrot shows something weird.
The first 10 letters, "python2 ex", shouldn't be there. It gets "stuck" there if i scroll in the term history.
Anyone knows what/why/how this happens? Just annoying, no real problem....
Last edited by melw (2012-09-21 19:09:50)
I know I'm paranoid, but am I paranoid enought....
Offline
In the left term in this scrot shows something weird.
The first 10 letters, "python2 ex", shouldn't be there. It gets "stuck" there if i scroll in the term history.
Anyone knows what/why/how this happens? Just annoying, no real problem....
What do you mean that it gets stuck there?
Have you tried pressing the down arrow-key/page down to see if the line would go blank?
Last edited by lspci (2012-09-15 12:16:10)
Offline
I see weird effects on xterm, once the line gets to the bottom of the windows and a scroll will happen. This during the input.
The line will get up of one and the text will be overwritten and in the wrong place.
do it good first, it will be faster than do it twice the saint ![]()
Offline
Maybe a problem with the $TERM variable. What's your current one.
Offline
melw wrote:In the left term in this scrot shows something weird.
The first 10 letters, "python2 ex", shouldn't be there. It gets "stuck" there if i scroll in the term history.
Anyone knows what/why/how this happens? Just annoying, no real problem....
What do you mean that it gets stuck there?
Have you tried pressing the down arrow-key/page down to see if the line would go blank?
lspci: I mean that those 10 letters are there when i use up/down arrow to scroll through the history and get stuck until I execute a command or something. Then the line gets back to normal again. But the "stuck" part isn't a part of the command. It's just text, like it would be a part of my PS1 for a moment.
The Saint: This happens in both urxvt and xterm for me and all the time as long as i scroll through the history.
x33a: I echoed $TERM and got "xterm" (without the " ofcourse).
And as i said before. Is more of an annoying thing, no real problem, really...
I know I'm paranoid, but am I paranoid enought....
Offline
lspci wrote:melw wrote:In the left term in this scrot shows something weird.
The first 10 letters, "python2 ex", shouldn't be there. It gets "stuck" there if i scroll in the term history.
Anyone knows what/why/how this happens? Just annoying, no real problem....
What do you mean that it gets stuck there?
Have you tried pressing the down arrow-key/page down to see if the line would go blank?
lspci: I mean that those 10 letters are there when i use up/down arrow to scroll through the history and get stuck until I execute a command or something. Then the line gets back to normal again. But the "stuck" part isn't a part of the command. It's just text, like it would be a part of my PS1 for a moment.
The Saint: This happens in both urxvt and xterm for me and all the time as long as i scroll through the history.
x33a: I echoed $TERM and got "xterm" (without the " ofcourse).
And as i said before. Is more of an annoying thing, no real problem, really...
Oh, you mean like when a line of commands suddenly, instead of continuing onto a new line simply overwrites the current line, but actually doesn't?
Offline
This oddity is going to be difficult to track down. I don't have the problem with my xterm instances. I have a plain undecorated window for xterm, with no menus and no scrollbar, just as you apparently do.
The only xterm scroll options I have set in my .Xdefaults are these:
XTerm*scrollBar: false
XTerm*jumpScroll: true
XTerm*multiScroll: trueDoes it happen with a one line PS1, too? It won't hurt to check.
You could try adding "shopt -s checkwinsize" to your .bashrc. I can't remember exactly what annoyance made me add that to my shell options, I do remember it was some sort of uncleared screen after a program was run.
`checkwinsize'
If set, Bash checks the window size after each command and,
if necessary, updates the values of `LINES' and `COLUMNS'.
Offline
I suspect it's your prompt not cooperating with readline. To test, try a more 'vanilla' prompt. To fix, ensure you're encolsing nonprinting characters in \[...\] in your prompt.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
You could try adding "shopt -s checkwinsize" to your .bashrc.
I'm testing this and it seems the clue.
FYI the problem appear on xtem uxterm and gnome-terminal, which might be based on xterm.
BTW I've a coloured prompt.
I'm gonna test this I'll be back to see if it's fixed
do it good first, it will be faster than do it twice the saint ![]()
Offline
Offline
Myne are escapated, but was doing the same. The fix seems on shopt -s checkwinsize. Still a minor issue that some time it doesn't display the history line correctly. Specially case when there're long lines.
do it good first, it will be faster than do it twice the saint ![]()
Offline
That worked really well! Solved ![]()
I know I'm paranoid, but am I paranoid enought....
Offline