Comment 6 for bug 1297051

> Please excuse my ignorance but I don't know how to do that. Can you tell
> me what commands to type?
> Is it in a repository somewhere or do I have to build from source?

You need to build from source, which goes something like this:

wget ftp://ftp.gnome.org/pub/GNOME/sources/vte/0.37/vte-0.37.2.tar.xz
tar xf vte-0.37.2.tar.xz
cd vte-0.37.2
patch -p1 < [the patch filename that fixes this bug]
./configure
[if there are any errors, install the missing packages and re-run]
make
./src/vte-2.91 --encoding=latin1 # or whichever other encoding you wish to use
[and then try your application in this new window

> Pretty much any sensible application should do that (regarding CSI at
> least) because ... why transmit two characters (ESC [) instead of one
> character (0x9B)?

Pretty much all sensible applications have been using UTF-8 for almost a decade now, and in this encoding both of these escapes take up 2 bytes. And these days when you watch videos of cats online, who cares about 1 more byte? :)

So far you're the only person who filed this bug against VTE, and it doesn't even work in xterm with UTF-8, which implies that the usage of C1 is extremely uncommon.

> In my case the remote system is a mix of built-in programs (for example,
> the editor) and custom-written programs, most of which assume that a
> one-character CSI (0x9B) works.

Really out of curiosity, could you please name a few of these "built-in programs (for example, the editor)" along with the system they're running on? (I don't care about the custom-written programs that much, but I do care about those that have a potential that other people also use them.)

That being said, if the patch works for you, I'd be happy to apply it.