wsvt25 is part of upstream ncurses and AFAIK is meant to be the terminfo description for wscons vt220 emulation. I would base any improved entries on it, either as changes (if they are always right) or addons like eg screen-bce.
Upstream ncurses has taken changes to wsvt25 before. I at least would be pretty reluctant to include full terminfo entries as local changes in OpnBSD. If possible try to get them upstream. I think changing /etc/ttys is unlikely to happen, there are systems out there with ancient/crappy terminfo databases and it is easy just to change it yourself if you want. On Sun, Sep 04, 2011 at 09:00:56PM +0400, Alexei Malinin wrote: > Paolo Aglialoro wrote: > > 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? > > > Paolo Aglialoro wrote: > > Does your config correctly support keys like Home, End, Del? > > It would be then really interesting to have it inside term options, > > whether > > or not default, but at least as choice. > > > > Christian Weisgerber wrote: > >>>> "wsvt25" is a better description, but if you log into a non-OpenBSD > >>>> system that terminal name may be unknown. > >>> Do you mean that if I log into a non-OpenBSD system "wsvt25" may be > >>> unknown? > >> What I mean is this: You log into the OpenBSD console with > >> TERM=wsvt25. Things are fine. Then from within this session you ssh to > >> a non-OpenBSD system where "wsvt25" is not known. > >> > >> $ vi > >> vi: No terminal database found > >> $ less > >> WARNING: terminal is not fully functional > >> > >> Etc. > > I think that: > - wsvt25 may be unknown to the remote system (as Christian wrote above) > as well as pccon > - pccon can be included in termtypes.master (the last is constantly > changing) so that people will have a choice (as proposed above by > Paolo) > - we can leave vt220 as the default terminal in /etc/ttys, > wait a several years until the changes of termtypes.master spread > widely enough, and then think about changing the default terminal > for OpenBSD > > > -- > Alexei Malinin > > > > 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.
