On 2015-06-30 16:09:29 +0100, Stephane Chazelas wrote: > 2015-06-30 16:45:59 +0200, Vincent Lefevre: > > On 2015-06-30 15:04:17 +0100, Stephane Chazelas wrote: > > > From a UTF-8 terminal: > > > > > > luit -encoding 'ISO 8859-1' ssh host-known-to-use-latin1 > > > > This is not very good, because the default encoding on the remote > > machine may change without notice. > > That's also potentially affected by the remote user's > .cshrc/.bashrc/.zshenv...
Actually more by a change by the admin. > > > Or: > > > > > > ssh -t host luit > > > > Any solution without writing "luit" explicitly? > > Other solutions can be GNU screen which can translate encodings > on the fly. GNU screen doesn't allow one to use the alternate screen, and there would be the same problem: how to use GNU screen without writing it explicitly? For instance: ssh host my_command where my_command is automatically run under GNU screen. With charmap transmission, everything is transparent. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
