On 05/08/14 10:17, Egmont Koblinger wrote: > ./src/vte-2.91 --encoding=latin1 # or whichever other encoding you > wish to use An additional comment on this ... if I use latin1 encoding then normal shell commands like 'man' have glitches in their output, presumably because they use Unicode characters and assume, for example, UTF-8 encoding. If I use utf8 encoding then my remote application does not work at all (because the remote application is completely incapable of sending UTF-8 encoding).
This is OK for me. I just means that I should use the terminal so that it automatically SSHs to the remote system, selecting the correct encoding for that system (latin1). That is, I need to have a terminal that is dedicated to the session on the remote system, while keeping that separate from any terminal that is on my local computer. That is all fine for me. What does not work is to make a terminal, type some local commands, then SSH to the remote system - unless I change profile around the SSH. (Of course it would be nice if this were automatic.) Strangely, while in the released gnome-terminal I can right mouse click and change profile dynamically, in the program that I built from source as per your instructions, this feature seems to have disappeared. Is there still some way of maintaining and selecting profiles? Regards Derek -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1297051 Title: gnome-terminal doesn't recognise C1 controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte3/+bug/1297051/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
