When I look at gnome-terminal via the AT-SPI, I'm noticing some curious behavior when I hit backspace while editing the command line.  When I do this, the terminal seems to want to pad out the remainder of the line (i.e., from the caret to the right edge of the window) with spaces, issuing a text-inserted event for those spaces.  In addition, when I press backspace, the text-deleted event is giving me incorrect information about what was deleted (it seems to tell me where the cursor ended up instead of what was deleted).

Related to the backspace problem, if I press the space key before I've done the backspace, I get text-inserted events for the space.  If I then press the space key after I've done the backspace, however, I don't get text-inserted events anymore; I just see caret-moved events.  (I do see, of course, text-inserted events for other characters at this point, but not for spaces.)

Ideally, this backspace padding would not happen and we would also get more reliable information when text is deleted.  I've dug into the gnome-terminal code a little bit to try to find out where this is happening, but I've had little success.  I'm curious if a gnome-terminal guru might be able to help or point me in the right direction.  It would help me identify the source of the problem and I could then file more appropriate bugs.