Didn't know about the TERM variable pass over ssh... ...anyway, on those systems with many screen consoles like i386/amd64, one could have a tty with vt220 to go ssh and another to deal correctly with keyboard, that would be cool. So, still having that layout inside terminals list could be way interesting (after all, many people prefer pressing Home, End and Del instead of Ctrl-A/E/D).
The only question would be for those systems which do not support this like sparc64 (even if, I know, the question was born around amd64, but then the philosophy would become extensible...): does tmux inherit the TERM variable in the virual sessions opened or is there some degree of freedom? On Sat, Sep 3, 2011 at 12:42 PM, Stuart Henderson <s...@spacehopper.org>wrote: > On 2011-09-02, Alexei Malinin <alexei.mali...@mail.ru> wrote: > > Stuart Henderson wrote: > >> On 2011-09-02, Alexei Malinin <alexei.mali...@mail.ru> wrote: > >>> Christian Weisgerber wrote: > >>>> but if you log into a non-OpenBSD > >>>> system that terminal name may be unknown. > >>> terminal descriptions proposed by me are intended for > >>> OpenBSD consoles only (these descriptions are of > >>> questionable value in other systems) > >> > >> Do you never ssh or telnet from OpenBSD to another type of system? > > > > of course I do ssh/telnet to other systems, > > I understand Christian's notice, I mean that > > my terminal descriptions are of questionable value > > for other systems _consoles_ > > ssh and telnet pass the TERM variable to other systems. > > If you are using a TERM which the other system doesn't understand, > they will fall back to a dumb terminal, which can be very annoying. > There are workarounds but they can be annoying too. > > So, while it might be useful to have this in termcap (or adjust the > existing wsvt* console entries which may perhaps be a better option), > it doesn't seem sensible to set it by default in /etc/ttys.
