Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Feb 2007 10:33:20 -0500
From:      Thomas Dickey <>
Subject:   Re: ssh to VMS - terminal problems
Message-ID:  <>
In-Reply-To: <45dd5ca7.ae4LWHr14/>
References:  <> <> <> <45dd5ca7.ae4LWHr14/>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 22, 2007 at 01:04:39AM -0800, wrote:
> > > yes - VMS only knows about DEC-compatible terminals.  None of
> > > the *BSD console emulators do well enough to be usable on VMS.
> > >=20
> > > xterm supports ANSI color, VT220 emulation and UTF-8
> > > There's an faq at
> > >
> > >
> Which is fine if one doesn't mind having to fire up X.  Another
> possible approach would be to run ports/sysutils/screen, which
> "should" provide a decent VT100 over just about anything with a
> terminfo better than "dumb" or "unknown" :)


screen doesn't use the fancier features from terminfo (and will do interest=
but unuseful things if it is exposed to them).

It's a decent vt100 for the same issues: applications running vi.
Read the section on bugs (from its manpage):

     o  Screen has  no  clue  about  double-high  or  double-wide
        characters.  But  this  is  the only area where vttest is
        allowed to fail.

     o  Screen does not make use of hardware tabs.

However, that comment about vttest overlooks some of the keyboard
issues (such as repeating keys) that screen has no control over.
There are several terminals smarter than dumb/unknown that screen
cannot elevate or transform into a vt100...

Thomas E. Dickey

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.0.6 (SunOS)
Comment: For info see



Want to link to this message? Use this URL: <>