After running emerge, the backspace key in mrxvt does not work anymore, but i have to use CTRL+Backspace instead. calling stty dec fixes the problem. Reproducible: Always Steps to Reproduce: 1. start mrxvt 2. emerge some small package 3. press backspace Actual Results: some junk is displayed on the console, backspace not working. it isn't enough to just start emerg for example with -a and then choosing "no". backspace keeps working in that case. portage really needs to start building the package to destroy the backspace key...
Maybe it is related to whatever $PROMPT_COMMAND contains. Anyway, the relevant code should be in portage's output.py file.
hmm... recently this even occurs on a gentoo linux gnome-terminal when ssh'ing to an interix box...
termcap?
Are you still experiencing this?
i can't reproduce this with mrxvt 0.5.4 available in the portage. Backspace is working here after emerging a package.
(In reply to comment #5) > i can't reproduce this with mrxvt 0.5.4 available in the portage. > Backspace is working here after emerging a package. this bug is interix specific (now that i saw it again, i'm gonna retest this asap to get it closed...), did you test on interix?
yes, this still happens. after running an emerge, backspace produces a ^?. i need to "stty erase ^?" to make it work again. i just noticed that SHIFT+backspace does work as expected ;)
i tried to run tic to get terminfo up to date, and also tried TERM=xterm, with no difference at all.
(In reply to comment #6) > (In reply to comment #5) > > i can't reproduce this with mrxvt 0.5.4 available in the portage. > > Backspace is working here after emerging a package. > > this bug is interix specific (now that i saw it again, i'm gonna retest this > asap to get it closed...), did you test on interix? Hello Markus, cancel my post, I am using x86_64. I don't use interix. sorry for the confusion.
(In reply to Markus Duft from comment #6) > (In reply to comment #5) > > i can't reproduce this with mrxvt 0.5.4 available in the portage. > > Backspace is working here after emerging a package. > > this bug is interix specific (now that i saw it again, i'm gonna retest this > asap to get it closed...), did you test on interix? I just took on mrxvt. Is this issue still of interest? interix is pretty marginarl and I wouldn't know where to begin.
