It was a series of big patches heavily modifying the behavior. They're clearly not suitable to be backported to a stable distro. There's no self-contained tiny fix available for this problem. And since it's fixed in mainstream gnome-terminal, I have absolutely no interest in putting any effort into this.
You've just reported this bug towards trusty (1.5 years old) and precise (3.5 years old). I can't remember anyone ever reporting the same issue before, so it's apparently not an important one.
There are way more important vte issues in Ubuntu's bugtracker with one-line fixes that noone cares backporting.
It's fixed in Wily, and Xenial LTS is out in less than half a year.
Fixed packages for trusty are probably available from Gnome3 staging. Or you can use any other emulator as a workaruond for the time being.
And, anyways, iso2022 is a terrible encoding, and everybody should've switched to UTF-8 a long time ago.
No, sorry, not.
It was a series of big patches heavily modifying the behavior. They're clearly not suitable to be backported to a stable distro. There's no self-contained tiny fix available for this problem. And since it's fixed in mainstream gnome-terminal, I have absolutely no interest in putting any effort into this.
You've just reported this bug towards trusty (1.5 years old) and precise (3.5 years old). I can't remember anyone ever reporting the same issue before, so it's apparently not an important one.
There are way more important vte issues in Ubuntu's bugtracker with one-line fixes that noone cares backporting.
It's fixed in Wily, and Xenial LTS is out in less than half a year.
Fixed packages for trusty are probably available from Gnome3 staging. Or you can use any other emulator as a workaruond for the time being.
And, anyways, iso2022 is a terrible encoding, and everybody should've switched to UTF-8 a long time ago.