Gecko [ www.jdcpatala.org ]

Name	Size	Permission
README.Debian	1.77 KB	-rw-r--r--
README.i18n.gz	3.12 KB	-rw-r--r--
changelog.Debian.gz	1.74 KB	-rw-r--r--
copyright	8.26 KB	-rw-r--r--
ctlseqs.ms.gz	36.23 KB	-rw-r--r--
ctlseqs.txt.gz	33.72 KB	-rw-r--r--
xterm.faq.gz	73.33 KB	-rw-r--r--
xterm.faq.html	377.16 KB	-rw-r--r--
xterm.log.html	561.22 KB	-rw-r--r--
xterm.termcap.gz	4.37 KB	-rw-r--r--
xterm.terminfo.gz	14.15 KB	-rw-r--r--

Code Editor : xterm.faq.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">

<title>XTerm &ndash; Frequently Asked Questions (FAQ)</title>
 <link rel="author" href="mailto:dickey@invisible-island.net">
 <meta http-equiv="Content-Type" content=
 "text/html; charset=us-ascii">
 <meta name="keywords" content=
 "xterm, terminal, vt220, vt420, 256-colors, UTF-8">
 <meta name="description" content=
 "xterm is the standard terminal emulator for the X Window System. This page gives some background and pointers to xterm resources.">
 <link rel="SHORTCUT ICON" href="/img/icons/xterm.ico" type=
 "image/x-icon">
 <link rel="stylesheet" href="/css/simplestyle.css" type=
 "text/css">
 <link rel="stylesheet" href="/css/inline-code.css" type=
 "text/css">
 <link rel="stylesheet" href="/css/xterm-icons.css" type=
 "text/css">
 <style type="text/css">
 @import "/css/simplenavXX.css" all;
 </style>
 <meta name="viewport" content=
 "width=device-width, initial-scale=1">
</head>

<a href="/">http://invisible-island.net/</a><a href=
 "./">xterm/</a> 
 Copyright &copy; 1997-2018,2019 by Thomas E. Dickey

<hr>

<a href=
 "http://invisible-island.net/xterm/xterm.faq.html">Here</a> is
 the latest version of this file.

<h1 class="no-header">XTerm &ndash; Frequently Asked Questions
 (FAQ)</h1>

<li><a href="#what_is_it">What is XTerm?</a></li>

<li><a href="#who_did_it">Who wrote
 XTerm?</a></li>

<li><a href="#what_platforms">What platforms does it run
 on?</a></li>

<li><a href="#latest_version">What is the latest version?</a></li>

<li><a href="#other_versions">What versions are
 available?</a></li>

<li><a href="#compare_versions">Comparing versions, by
 counting controls</a></li>

<li><a href="#frequent_problems">Frequent problems</a></li>

<li><a href="#known_bugs">Known Bugs in
 XTerm and Look&ndash;alikes</a></li>

<li><a href="#building_it">How do I build
 XTerm?</a></li>

<li><a href="#report_bugs">How do I report bugs?</a></li>

<li><a href="#more_info">Additional Information</a></li>

<li><a href="#future_work">Ongoing/future work</a></li>
 </ul>
 </div>

<h2 id="what_is_it-id"><a name="what_is_it" id="what_is_it">What
 is XTerm?</a></h2>

From the manual page:

<blockquote class="code-block">
 The xterm program is a terminal emulator for the X Window
 System. It provides DEC VT102/VT220 and selected features from
 higher-level terminals such as VT320/VT420/VT520 (VTxxx). It
 also provides Tektronix 4014 emulation for programs that cannot
 use the window system directly. If the underlying operating
 system supports terminal resizing capabilities (for example,
 the SIGWINCH signal in systems derived from 4.3bsd), xterm will
 use the facilities to notify programs running in the window
 whenever it is resized.
 </blockquote>

That is, xterm (pronounced "eks-term") is a
 specific program, not a generic item. It is the standard
 X terminal emulator program.

This FAQ presents various useful bits of information for both
 the specific program as well as other programs that imitate
 it.

As a stylistic convention, the capitalized form is
 "XTerm", which corresponds to the X resource class name.
 Similarly, uxterm becomes "UXTerm".

<h2 id="who_did_it-id"><a name="who_did_it" id="who_did_it">Who
 wrote XTerm?</a></h2>

I've been working on xterm since early 1996 (see my <a href=
 "xterm.log.html">changelog</a> for details).

But the program is much older than that.

<h3 id="pre_history-id"><a name="prehistory" id="prehistory">A
 Prehistory Perspective</a></h3>

A lot of people, cited at the bottom of the manual page wrote
 the original xterm program, maintained by the X Consortium (later
 part of The Open Group &ndash; I'm well aware of the distinction,
 but am citing when the work was done, not who the current owner
 may be). There is no changelog, and it is not clear who did what.
 Email from Jim Gettys (September 1998) provides some
 background:

<blockquote class="code-block">
 Cast of thousands...

To give a bit of history, xterm predates X!

It was originally written as a stand-alone terminal emulator
 for the VS100 by Mark Vandevoorde, as my coop student the
 summer that X started.

Part way through the summer, it became clear that X was more
 useful than trying to do a stand alone program, so I had him
 retarget it to X. Part of why xterm's internals are so
 horrifying is that it was originally intended that a single
 process be able to drive multiple VS100 displays. Don't hold
 this against Mark; it isn't his fault.

I then did a lot of hacking on it, and merged several
 improved versions from others back in.

Notable improvements include the proper ANSI parser, that
 Bob McNamara did.

The Tek 4010 support came from a guy at Smithsonian
 Astrophysical Observatory whose name slips my mind at the
 moment.

Ported to X11 by Loretta Guarino.

Then hacked on at the X Consortium by uncounted people.
 </blockquote>

There is a git repository <a href=
 "http://cgit.freedesktop.org/~alanc/xc-historical/log/xc/programs/xterm/">
 here</a> which gives some more of xterm's prehistory.

Email from Doug Mink (October 1999) provides more
 background:

<blockquote class="code-block">
 I was checking out the newly revised AltaVista search engine
 to see what was on the net about xterm, and I found your pages.
 I can add to the FAQ in that I was the "guy at the Smithsonian
 Astrophysical Observatory" Jim Gettys refers to. I am listed at
 the end of the man page under authors. What happened was that I
 was hired by SAO (after leaving the research staff at MIT) in
 October 1985 to write analysis software for the Spacelab 2
 Infrared Telescope which was to fly on the Space Shuttle in
 1985 less than six months after I was hired. I came with a tar
 tape full of software I had written for Unix and Tektronix
 terminals, but I was presented with a VS100 terminal which had
 an early version (X6 or so) of xterm, with no graphics
 capabilities. SAO is at Harvard, across Cambridge from MIT,
 where Jim Gettys was detailed from DEC to the X project, and
 Jim had connections with SAO, having worked here after college
 (MIT, where we had both worked at the observatory at various
 times); he was still sharing an apartment with an SAO colleague
 of mine, too. Anyway, everyone decided that since I knew
 Tektronix commands pretty well, and our group desparately
 needed the graphics capabilities, it would be a good use of my
 time to implement a Tektronix terminal emulator under X. So I
 set to work learning more C--I had only written a couple of
 wrappers to C I/O routines so I could use them with my Fortran
 software--and wrote a Tektronix emulator. The only X
 documentation at the time was the code itself. While I was at
 it, I wrote an improved Tektronix emulator for our Imagen laser
 printer which used the full resolution of that 300 dpi printer
 instead of the effective 100 dpi (i.e. jaggy) emultator
 distributed with the printer. The original xterm Tek emulator
 shared a window with the VT100 emulator, much like on the VT240
 terminals which I had been using at MIT before I came to
 Harvard. With a VAX 750 running several VS100's, window
 creation was sloowww, so sharing a window was the quickest way
 to do things, and all of my software was written for that mode
 of operation, anyway. While I wrote the emulator so that my
 software would work on it, it was tested by the X group against
 a BBN graphics package, the name of which slips my mind right
 now.

Anyway, 15 years later, I am still using xterm and some of
 the same mapping software I wrote the emulator for. And I am
 still at the Smithsonian Astrophysical Observatory.
 </blockquote>

<h3 id="my_history-id"><a name="my_history" id="my_history">My
 Involvement</a></h3>

My involvement with xterm through XFree86
 began at the <a href="/xterm/xterm.html#history">end of 1995</a>.
 This website has been "here" since 2001/6/5, replacing my
 ClarkNet page. I started the ClarkNet page 1996/12/31, as a
 followup to the <a href=
 "/ncurses/ncurses-license.html#patch_961224">release of ncurses
 4.0</a>) which featured xterm as one of the 16 programs I was
 involved with. From the outset, the page provided a link to a
 snapshot of the current source. Copies of patches which I sent to
 XFree86 were available on the ftp area.

XFree86 had its sources in CVS, but (like others in that era),
 were not directly visible to random developers. That came later.
 I started by downloading the sources (30Mb of compressed
 tar-files on a 56Kb phone connection took about 6 hours) and
 updating them with patches from the XFree86 mailing list.

Like the other programs that I worked on with others (<a href=
 "/vile/vile.html">vile</a>, <a href="/tin/tin.html">tin</a>,
 <a href="/lynx/lynx.html">lynx</a>), I set up an RCS archive to
 track my changes locally before sending patches to the
 development list. As the XFree86 developers issued new patches, I
 would re-synchronize my archive. Later, XFree86 provided CVS
 (initially readonly). I was granted commit privileges on this
 <a href="/ansification/ansify-xfs-cve.html#xfree86_work">in
 November 2000</a>.

Throughout this period, my work on xterm was
 released as part of XFree86. It was rare for a separate package
 to be provided. That was due to the potential conflict between
 the install procedures. Users of the downloads from my web/ftp
 site were predominantly individual developers.

There were exceptions. Christian Weisgerber proposed a package
 for FreeBSD ports later in 1999 (<a href=
 "https://web.archive.org/web/20130801223050/http://www.mavetju.org/mail/view_message.php?list=freebsd-ports&amp;id=578273">ports/15545:
 new port: x11/xterm</a>, followup in <a href=
 "http://marc.info/?t=102422536300028&amp;r=l&amp;=2">March
 2000</a>). However, that was an exception. None of the Linux
 distributions provided a separate package before 2003 (when Mike
 Harris created a package of <a href=
 "xterm.log.html#xterm_177">patch #177</a> for Red Hat). Again
 that is more of an exception than a rule:

<ul>
 <li>SuSE's package began October 23, 2004 with <a href=
 "xterm.log.html#xterm_196">patch #196</a>.</li>

<li>Mandriva's package began October 22, 2005 with <a href=
 "xterm.log.html#xterm_205">patch #205</a>.</li>

<li>The Debian package for xterm began in January 6, 2006 with
 <a href="/xterm/xterm.log.html#xterm_204">patch #204</a>.</li>
 </ul>

Given that context (sources distributed via XFree86 CVS,
 releases via XFree86), the statement made by an Xorg hacker
 <a href=
 "http://lists.freedesktop.org/archives/xorg/2005-January/005847.html">
 early in 2005</a> asserting that "It has not been maintained by
 anyone within the XFree86 or X.org trees for many years" was at
 best misleading.

After the "<a href=
 "xterm.faq.html#xterm-xorg">fork</a>"&nbsp;(sic) of Xorg in 2004,
 I continued to commit changes for xterm in <a href=
 "http://cvsweb.xfree86.org/cvsweb/xc/programs/xterm/">XFree86
 CVS</a> until <a href="/xterm/xterm.log.html#xterm_216">patch
 #216</a> in mid-2006. I stopped at that point because it was not
 possible to incorporate changes into xterm which were not sent to
 me first. I still send patch announcements to both the XFree86
 and Xorg mailing lists, of course.

<h3 id="forward_history-id"><a name="forward_history" id=
 "forward_history">Focus of this FAQ</a></h3>

This FAQ is oriented toward the version of xterm originally
 distributed with XFree86 (more commonly known as modern, or "new
 xterm", with a corresponding terminal description "xterm-new"),
 which was based on the X11R6.3 xterm, with the addition of ANSI
 color and VT220 controls.

<li><a href="#whatis_state_table">What is a State Table?</a></li>

<li><a href="#why_not_vt320">Why not emulate VT320?</a></li>

<li><a href="#why_vt420">Why emulate VT420?</a></li>

<li><a href="#why_not_vt520">Why not emulate VT520?</a></li>
 </ul>

The manual page mentions a VT220. Most terminal emulators
 documentation talk about VT100. But a VT100 is a rather limited
 subset of what people expect:

<ul>
 <li>VT100s have no function keys. Arguably, PF1-PF4 are
 function keys. My keyboard has 12 function keys.</li>

<li>VT100s do not do <a href=
 "/ncurses/ncurses.faq.html#vt100_color">color</a>.</li>
 </ul>

Initially, I was only interested in making colors workable for
 curses programs.

Later, I noticed that xterm had some support for what would
 now be termed as ISO-2022. That was a VT220 feature which
 preceded ISO-2022 called National Replacement Character
 sets. In any case, it was not a VT100 feature. There were some
 missing pieces. So I decided to fill in those pieces and make
 xterm a VT220 emulator. (VT220s do not do ANSI color
 either&mdash;the missing pieces were in other areas).

XTerm also provides features that are in
 neither VT100 nor VT220, which are used by other programs as
 "xterm emulation".

<ul>
 <li>set (and retrieve) window- and icon-labels using escape
 sequences.</li>

<li>interpret mouse clicks as escape sequences that can be read
 by a program.</li>
 </ul>

By the way, the control string used for setting the titles was
 not in a standard format:

<ul>
 <li>In X10 (1988), the string was simply terminated by any
 nonprinting character.</li>

<li>X11R4 (1989) modified that to ensure that the nonprinting
 character is an ASCII BEL (control/G).</li>

<li>There is no explanation in the (sketchy) notes distributed
 with the X11R4 xterm; in retrospect it seems that the most
 likely explanation for the choice is that it was simpler to
 implement in shell scripts than <code>ESC&nbsp;\</code>.</li>
 </ul>

ECMA-48 (the standard) does not describe this particular
 control, but prescribes its format (an <a href=
 "ctlseqs/ctlseqs.html#h2-Operating-System-Commands">operating
 system command</a>). It does not use a
 <code>BEL</code>.

I revised that area <a href=
 "/xterm/xterm.log.html#xterm_24">starting in 1996</a>,

<ul>
 <li>first to use xterm's state table for handling the input,
 and then</li>

<li>to accept the standard string terminator as well.</li>
 </ul>

In addition to implementing the VT220's National
 Replacement Character sets (see vttest <a href=
 "/vttest/vttest-nrcs.html">screenshots</a>), I added other
 features to emulate the successive models of DEC terminals. The
 <a href=
 "manpage/xterm.html#VT100-Widget-Resources:decTerminalID"><code>decTerminalID</code></a>
 resource (in <a href="xterm.log.html#xterm_29">1999</a>) lets
 users select the emulation to use. Because many of my changes
 were extensions (features not in any of DEC's terminals)
 and because well-behaved VT100 applications would not use
 features from higher-level terminals it was not initially
 important to prevent use of those by applications which assumed
 they were using just a VT100. Knowledgable users could easily
 configure xterm to emulate a VT220. In <a href=
 "xterm.log.html#xterm_280">2012</a>, I changed the default from
 VT100 to VT420.

<h3 id="whatis_state_table-id"><a name="whatis_state_table" id=
 "whatis_state_table">What is a State Table?</a></h3>

That was mentioned regarding the title strings.
 XTerm uses a state machine to handle incoming
 characters. That is essentially what a real terminal does. Other
 "xterm" terminal emulators typically do not do this, which makes
 them not do well with <a href=
 "/vttest/vttest.html">vttest</a>.

<h3 id="why_not_vt320-id"><a name="why_not_vt320" id=
 "why_not_vt320">Why not emulate VT320?</a></h3>

You could do that (by changing <code>decTerminalID</code>, but
 the results were not that interesting). In retrospect, the VT320
 was a stopgap implementation designed to bridge between the VT200
 series and the VT420. It provided a standard codepage (for ISO
 Latin-1).

While it had other features not found in the VT200-series,
 most of those are less useful in a terminal emulator. I did adapt
 the ECMA-48 scrolling operations which the VT320
 interpreted as panning the visible display in the
 terminal's memory. Expect some difference there (if you can find
 an application on VMS which used the feature).

The VT320 was popular with developers of commercial terminal
 emulators, whose literature referred to it as supporting ANSI
 color. It did not do this.

<h3 id="why_vt420-id"><a name="why_vt420" id="why_vt420">Why
 emulate VT420?</a></h3>

The VT420 was interesting because it provided two features
 that could be useful:

<ul>
 <li>rectangles</li>

<li>left/right margins (like the top/bottom scrolling
 margins)</li>
 </ul>

A VT420, of course, supports all of the features in VT320, in
 turn all of the features in VT220, and in turn VT100. Users would
 not lose features by changing the default emulation to VT420. By
 changing the default emulation, most users would automatically be
 able to use applications (such as <code>tmux</code>) that could
 perform better if the left/right margin feature is available. I
 changed the emulation to VT420 in 2012 for this reason.

XTerm does not emulate some esoteric features (such as dual
 sessions) because those require hosts using special software, and
 no publicly-available documentation was available.

<h3 id="why_not_vt520-id"><a name="why_not_vt520" id=
 "why_not_vt520">Why not emulate VT520?</a></h3>

Again, the VT500-series is less interesting because most of
 the features which are not hardware-specific (such as reporting
 transmission rate) are less useful.

However:

<ul>
 <li>the VT500-series provides additional codepages (like the
 VT320). XTerm does that.</li>

<li>the VT500-series supports some of the ECMA-48
 cursor-movement operations which had been overlooked in the
 previous terminals. XTerm does that (based on ECMA-48 itself,
 and later on DEC's documentation).</li>
 </ul>

As for the other features, most are not useful in emulation
 (since they are hardware-specific). Additionally, these less-used
 features are not documented precisely and since the only point of
 providing them would be for successful interoperability with
 legacy applications, some reverse-engineering would be needed to
 provide a faithful emulation. To date there are no known terminal
 emulators which do that.

<h2 id="what_platforms-id"><a name="what_platforms" id=
 "what_platforms">What platforms does it run on?</a></h2>

XTerm runs in all of the implementations of
 X11. As of 2000, I had built and run these since I started
 working on xterm in 1996:

<li>Digital Unix 3.2, 4.0, 5.0 (cc)</li>

<li>FreeBSD 2.2.6 to 6.0 (gcc 2.8)</li>

<li>Linux 2.0.0 to 2.6.26 (gcc 2.7.2 to 4.3)</li>

<li>SCO OpenServer 5 (cc, gcc).</li>

<li>Solaris 2.4, 2.5, 2.5.1, 2.6, 7, 8 (cc, gcc 2.7.2)</li>

<li>SunOS 4.1.1, 4.1.3 (gcc 2.7.2)</li>
 </ul>

The older configurations have X11R5 libraries. Only minor
 changes are needed to make xterm work on those systems. However,
 X11R6 provided better locale support, as well as new features
 such as the active icon. X11R7... not much to say there.

Since 2000, there have been many changes (including new
 platforms such as MacOS, NetBSD, OpenBSD, etc., as well as QNX,
 Cygwin, and Minix).

<h2 id="latest_version-id"><a name="latest_version" id=
 "latest_version">What is the latest version?</a></h2>

The most recent (and well supported) version of xterm is the
 one that I maintain:

<ul>
 <li><a href=
 "ftp://ftp.invisible-island.net/xterm/xterm.tar.gz">current
 source (ftp)</a></li>

<li><a href="/datafiles/release/xterm.tar.gz">current source
 (http)</a></li>
 </ul>

<h2 id="other_versions-id"><a name="other_versions" id=
 "other_versions">What versions are available?</a></h2>

There are several other versions of xterm, based on xterm's
 source. These include

<ul>
 <li><a href="#bug_ansi_xterm">ansi_xterm</a></li>

<li><a href="xterm.faq.html#bug_color_xterm">color_xterm</a></li>

<li><a href="#bug_cxterm">cxterm</a> (Chinese)</li>

<li><a href="#bug_hanterm">hanterm</a> (Korean)</li>

<li><a href="#bug_mxterm">mxterm</a></li>

<li><a href="#bug_nxterm">nxterm</a></li>

<li><a href="#bug_kterm">kterm</a> (Japanese)</li>

<li><a href="#bug_xterm_r6">xterm</a> (from X Consortium)</li>
 </ul>

There are similar programs not based on xterm's source, which
 are compatible to different degrees. These include

<ul>
 <li><a href="#bug_dtterm">dtterm</a></li>

<li><a href="#bug_emu">emu</a> (from X Consortium)</li>

<li><a href="#bug_eterm">Eterm</a></li>

<li><a href="#bug_gnometerm">GNOME Terminal</a></li>

<li><a href="#bug_multignome">Multi GNOME Terminal (MGT)</a></li>

<li><a href="#bug_mterm">mterm</a></li>

<li><a href="#bug_konsole">konsole</a></li>

<li><a href="#bug_mlterm">mlterm</a> (Multi Lingual)</li>

<li><a href="#bug_osso_xterm">osso-xterm</a></li>

<li><a href="#bug_roxterm">roxterm</a></li>

<li><a href="#bug_xgterm">xgterm</a></li>

<li><a href="#bug_xiterm">xiterm</a></li>
 </ul>

Some of these use the <a href="#vte_widget">VTE widget</a>.
 Since that supplies most of the terminal emulation, the remaining
 differences between programs using VTE tend to be at the level of
 the window manager (menus, borders, etc.). Other (older) programs
 which are based on reusable widgets include <a href=
 "#bug_dtterm">dtterm</a> and <a href=
 "xterm.faq.html#bug_emu">emu</a>.

(I am aware of a few others, such as xcterm,
 but have not seen a working version of these).

Finally of course, there are a multitude of programs which set
 TERM to "xterm", in the hope that applications will treat them
 the same as xterm. For example,

<ul>
 <li>PuTTY does this (see its FAQ <a href=
 "http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html#faq-term">
 A.5.1 What terminal type does PuTTY use?</a>). But its
 wrapping behavior is incompatible with xterm (and any vt100
 emulator). You can see this in the first menu entry for
 <a href="/vttest/vttest.html">vttest</a>.</li>

<li>VTE does this. But consider the list of problems with
 <a href=
 "https://bugzilla.gnome.org/buglist.cgi?quicksearch=vte">VTE</a>
 and with <a href=
 "https://bugzilla.gnome.org/buglist.cgi?quicksearch=gnome+terminal">
 GNOME Terminal</a>. The attitude of the developers is that by
 copying from xterm, they are entitled to do this
 whether or not the program actually matches xterm's terminal
 description. This is unchanged since the mid-2000s (see Debian
 <a href=
 "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368916">#368916</a>
 for example).</li>

<li>Konsole does this as well&mdash;intentionally as shown in
 <a href="https://bugs.kde.org/show_bug.cgi?id=145977">KDE
 #145977 &ndash; Konsole has a terminfo entry of its own; please
 change default $TERM</a>. The reasoning expressed there is
 that Konsole "should" match xterm. Incidentally, one of the
 comments (about xterm's support for mouse) cited as proof a
 <a href="http://www.linuxjournal.com/article/1136">page about
 Gpm</a> from Linux Journal which was more than 12 years
 old.</li>
 </ul>

Each of the programs noted here which are well-established and
 which are known to differ markedly from xterm have their own
 terminal descriptions in ncurses, to which TERM should be set.
 Otherwise, bug-reports are misdirected to <a href=
 "/ncurses/ncurses.html#download_database">ncurses</a> which
 should have been addressed by the respective developers of these
 programs. These include

<ul>
 <li><a href="/ncurses/terminfo.src.html#tic-_Eterm">Eterm</a></li>

<li><a href="/ncurses/terminfo.src.html#tic-gnome">gnome</a>
 (obsolete)</li>

<li><a href=
 "/ncurses/terminfo.src.html#tic-konsole">konsole</a></li>

<li><a href="/ncurses/terminfo.src.html#tic-mlterm">mlterm</a></li>

<li><a href="/ncurses/terminfo.src.html#tic-mrxvt">mrxvt</a></li>

<li><a href="/ncurses/terminfo.src.html#tic-putty">putty</a></li>

<li><a href="/ncurses/terminfo.src.html#tic-vte">vte</a>
 (preferred)</li>
 </ul>

<h2 id="compare_versions-id"><a name="compare_versions" id=
 "compare_versions">Comparing versions, by counting controls</a></h2>

Several of these programs are claimed (either by their
 developers, or their users) to emulate "most" of xterm. To me,
 "most" would be something quantifiable, e.g., 80 percent. To
 satisfy my curiousity, I wrote a script to extract the control
 sequence information from <a href=
 "xterm.faq.html#ctlseqs_ms">ctlseqs.txt</a>. This counts each
 control sequence, as well as the variations such as setting bold,
 color, inverse video. Then I (laboriously) inspected these
 terminal implementations:

<ul>
 <li>xterm patch #266 ("xterm-new")</li>

<li>X11R6.3 xterm (xterm-r6)</li>

<li>rxvt-unicode 9.09 (urxvt)</li>

<li>konsole 2.5.3</li>

<li>VTE 0.25.91 (vte), used in GNOME-Terminal and kindred.</li>
 </ul>

As of mid-November 2010, these were the latest
 implementations. I included data for the vt220 and vt102 to be
 able to contrast the various terminal emulators against
 those as well as xterm. There were:

<ul>
 <li>498 control sequences listed in the corresponding file for
 xterm patch #266.</li>

<li>192 of those are "primary", e.g., disregarding parameters
 such as those distinguishing bold from color.</li>

<li>37 of the primary control sequences have secondary
 sequences.</li>
 </ul>

For each control, there are three possibilities:

<ol>
 <li>"yes" &mdash; the terminal implements it, matching xterm.
 If xterm implements it, and it is a feature of vt220 or vt102,
 then in turn xterm's behavior must match vt220 or vt102.</li>

<li>"partial" &mdash; the terminal implements it, but its
 behavior does not match the reference noted above.</li>

<li>"no" &mdash; the terminal does not implement the
 control.</li>
 </ol>

The control sequences document lists a few controls which
 xterm does not (completely) implement, e.g.,

<ul>
 <li>key-repeat</li>

<li>enabling LEDs other than scroll-lock</li>
 </ul>

None of the other terminal emulators implements those
 either.

<table border="1" summary=
 "Comparing against the control sequences document">
 <caption>
 Comparing against the control sequences document
 </caption>

<th>partial</th>

<th>program</th>
 </tr>

<td>xterm-new</td>
 </tr>

<td>xterm-r6</td>
 </tr>

<td>urxvt</td>
 </tr>

<td>putty</td>
 </tr>

<td>konsole</td>
 </tr>

Modern xterm implements 188 primary controls. In this table,
 vte ranks lower than PuTTY because it does not support vt52
 emulation. This is not unusual, since the rxvt-based emulators do
 not, either. However, all vt100's provide this feature; programs
 lacking this are not really a vt100 emulator. On the other hand,
 PuTTY (which is not a vt100 emulator due to its incompatible
 wrapping behavior) supports this feature.

Aside from that, the various emulators implement much the same
 features from xterm. None implements as many as half of xterm's
 controls.

<table border="1" summary="Comparing against xterm">
 <caption>
 Comparing against xterm
 </caption>

<th>partial</th>

<th>program</th>
 </tr>

<td>xterm-new</td>
 </tr>

<td>xterm-r6</td>
 </tr>

<td>urxvt</td>
 </tr>

<td>putty</td>
 </tr>

<td>konsole</td>
 </tr>

DEC VT220 implements 96 primary controls. Modern xterm (as
 documented), implements most of the VT220. VTE implements fewer
 than half. The others are a little better. None of the others
 could be used as a real VT220.

<table border="1" summary="Comparing against vt220">
 <caption>
 Comparing against vt220
 </caption>

<th>partial</th>

<th>program</th>
 </tr>

<td>xterm-new</td>
 </tr>

<td>xterm-r6</td>
 </tr>

<td>urxvt</td>
 </tr>

<td>putty</td>
 </tr>

<td>konsole</td>
 </tr>

DEC VT102 (the actual flavor used for "vt100" in most cases),
 implements 68 primary controls. Again, VTE fares worst, and the
 others a little better.

<table border="1" summary="Comparing against vt102">
 <caption>
 Comparing against vt102
 </caption>

<th>partial</th>

<th>program</th>
 </tr>

<td>xterm-new</td>
 </tr>

<td>xterm-r6</td>
 </tr>

<td>urxvt</td>
 </tr>

<td>putty</td>
 </tr>

<td>konsole</td>
 </tr>

I have continued to add features to xterm:

<ul>
 <li>as of September 2013, it implemented 546 of 556 documented
 controls</li>

<li>as of October 2019, xterm implemented 713 of 723 documented
 controls.</li>
 </ul>

The other programs change far more slowly. As a result they
 implement a smaller fraction of xterm's repertoire in 2019 than
 in 2010. Even for cases where they implement a function, it may
 not work properly (see for example the screenshot of VTE in the
 <a href="/vttest/vttest-nrcs.html">vttest NRCS</a> examples).

In summary, none of the other terminal emulators emulates
 "most" of xterm. Instead, they implement the most commonly-used
 control sequences, and there are differences between them.

Not really problems, but frequently asked questions (the point
 of this, after all):

<ul>
 <li><a href="#how2_fsize">How do I change the font size?</a></li>

<li><a href="#how2_print">How do I print the screen?</a></li>

<li><a href="#how2_fkeys">How do I set up function keys?</a></li>

<li><a href="#how2_title">How do I set the title?</a></li>

<li><a href="#how2_blink">How do I make the cursor blink?</a></li>
 </ul>

<h3 id="how2_fsize-id"><a name="how2_fsize" id="how2_fsize">How
 do I change the font size?</a></h3>

XTerm uses fonts given as resource settings.
 You can switch between these fonts at runtime, using a menu. This
 is documented in the manpage, in the <a href=
 "/xterm/manpage/xterm.html#MENUS">MENUS</a> section.

X Consortium xterm provides popup menus, by pressing the
 control key together with the mouse button. Control right mouse
 button pops up the VT FONTS menu, from which you can
 select fonts that are specified in xterm's resources. Usually
 these are in increasing order of size.

Modern xterm provides the menu, plus a feature adapted from
 rxvt: pressing the shifted keypad plus or minus keys steps
 through the font menu selections, in order of their size.

XTerm's manpage does not document the syntax
 for X resources; it is done in the X documentation. If you are
 instead asking about a <a href=
 "xterm.faq.html#utf8_fonts">problem displaying a given font</a>,
 it may be due to a problem with your resource settings.

<h3 id="how2_print-id"><a name="how2_print" id="how2_print">How
 do I print the screen?</a></h3>

That depends on why you want to print it.

If you want a trace of an interactive session, you should use
 the script program. It records every character sent to
 the screen, recording them in a file <code>typescript</code>.
 There are two drawbacks to this approach:

<ul>
 <li>Every character is recorded. Even cursor movement, if you
 run an editor.</li>

<li>You must start a new shell to capture the
 <code>typescript</code> file.</li>
 </ul>

Well, what about logging? Some versions of xterm support
 logging to a file. In fact modern xterm does. Logging was dropped
 from X Consortium xterm during X11R5 due to security concerns.
 Those were addressed, but logging was not reinstated (in fact
 there is a related <a href="#bug_xterm_r6">bug</a> in xterm).
 Some people prefer this, because it is convenient: you can start
 and stop logging a popup menu entry. However

<ul>
 <li>Every character is recorded. Even cursor movement, if you
 run an editor.</li>

<li>Line drawing characters are translated to control
 characters, i.e., codes 0-31 (this may be fixed sometime, it is
 a problem inherited from X Consortium xterm).</li>
 </ul>

Both script and logging are useful for recording, but
 they require interpretation to make sense of the trace. You
 probably would not send that trace to a printer (not twice,
 anyway).

If you want to print the contents of the screen, modern xterm
 implements, as part of the VT100 emulation, an "attached"
 printer.

<ul>
 <li>The printer is really a pipe command, to which xterm
 writes.</li>

<li>You can print the current line, page, or continuously with
 the corresponding control sequences. That takes an application
 program which knows how to print the screen.</li>

<li>If you do not have an application, xterm has a popup menu
 entry to print the window.</li>
 </ul>

There are limitations and tradeoffs using the "attached"
 printer, because it is an emulation:

<ul>
 <li>The emulation is based on detailed documentation for a
 VT320. This states that control sequences are sent in each line
 to reset bold, underlining and other printable attributes, and
 to set them as needed. Your printer probably does not
 understand this sort of input. Use the xterm resource
 <code>printAttributes</code> to get more easily printed
 output.</li>

<li>The printer may hang. Not really, but it seems that way. If
 you use the "attached" printer from an application designed for
 the VT100 terminal, it is written with the assumption that the
 printer is a dedicated piece of hardware, printing onto a
 continuous form. Use the <code>printerAutoClose</code> resource
 to change xterm's behavior to close the printer pipe whenever
 the terminal is told to switch the printer offline.</li>
 </ul>

If you use the popup menu to print the screen, this will close
 the printer pipe unless it was already opened by the application
 running in xterm.

<h3 id="how2_fkeys-id"><a name="how2_fkeys" id="how2_fkeys">How
 do I set up function keys?</a></h3>

With modern xterm, this is relatively simple. So I'll answer
 that first.

With X Consortium xterm, you had partial support for DEC VTxxx
 function keys. Function keys F1 to F12 correspond to DEC's F1 to
 F12 (sort of). Actually, DEC's VT220 terminals do not have codes
 for F1 through F5. They are reserved for local functions. And the
 VT220 (and up) terminals have 20 function keys. So you cannot do
 anything with the F13 through F20 (i.e., DO, HELP and SELECT).
 Finally, though xterm is reputed to be VT100-compatible, it has
 no support for the VT100 keypad (PF1 to PF4, and the ","
 key).

Modern (XFree86) xterm changed the X Consortium codes for F1
 to F4 to match the VT100 PF1 to PF4, except when the emulation
 level is VT220 and up. In this case, it generates the same F1 to
 F4 codes as X Consortium xterm. Moreover, it adds a new resource
 <code>sunKeyboard</code>, which tells the program whether it has
 only 12 function keys (i.e., a Sun or PC keyboard). If so (this
 is selectable from the popup menu), you can use the control key
 with F1 to F12 to get F13 to F24, and use the "+" key on the
 keypad as an alias for "," (comma).

The emulation level for modern xterm is set via the resource
 <code>decTerminalID</code>, e.g., to 220 for a VT220. Once set,
 applications can set the emulation level up or down within that
 limit. DEC's terminals are configured in much the same way by a
 setup option.

That is the simple way, using a couple of new resources. The
 traditional way to get function keys involves translations. I
 have seen a few postings on the newsgroups that do this. Here is
 one from Bruce Momjian &lt;root@candle.pha.pa.us&gt; for a
 VT220:

xterm&nbsp;$XTERMFLAGS&nbsp;+rw&nbsp;+sb&nbsp;+ls&nbsp;$@&nbsp;-tm&nbsp;'erase&nbsp;^?&nbsp;intr&nbsp;^c'&nbsp;\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-name&nbsp;vt220&nbsp;-title&nbsp;vt220&nbsp;-tn&nbsp;xterm-220&nbsp;"$@"&nbsp;&amp;

</blockquote>

with the corresponding resources:

XTerm*VT100.translations:&nbsp;#override&nbsp;\n\ 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Home:&nbsp;string(0x1b)&nbsp;string("[3~")&nbsp;\n&nbsp;\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;End:&nbsp;string(0x1b)&nbsp;string("[4~")&nbsp;\n

vt220*VT100.translations:&nbsp;#override&nbsp;\n\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F1:&nbsp;string(0x1b)&nbsp;string("OP")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F2:&nbsp;string(0x1b)&nbsp;string("OQ")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F3:&nbsp;string(0x1b)&nbsp;string("OR")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F4:&nbsp;string(0x1b)&nbsp;string("OS")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F5:&nbsp;string(0x1b)&nbsp;string("[16~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F6:&nbsp;string(0x1b)&nbsp;string("[17~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F7:&nbsp;string(0x1b)&nbsp;string("[18~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F8:&nbsp;string(0x1b)&nbsp;string("[19~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F9:&nbsp;string(0x1b)&nbsp;string("[20~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F10:&nbsp;string(0x1b)&nbsp;string("[21~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F11:&nbsp;string(0x1b)&nbsp;string("[28~")&nbsp;\n&nbsp;\ 
 ~Shift&nbsp;&nbsp;&lt;Key&gt;F12:&nbsp;string(0x1b)&nbsp;string("[29~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F1:&nbsp;string(0x1b)&nbsp;string("[23~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F2:&nbsp;string(0x1b)&nbsp;string("[24~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F3:&nbsp;string(0x1b)&nbsp;string("[25~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F4:&nbsp;string(0x1b)&nbsp;string("[26~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F5:&nbsp;string(0x1b)&nbsp;string("[K~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F6:&nbsp;string(0x1b)&nbsp;string("[31~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F7:&nbsp;string(0x1b)&nbsp;string("[31~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F8:&nbsp;string(0x1b)&nbsp;string("[32~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F9:&nbsp;string(0x1b)&nbsp;string("[33~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F10:&nbsp;string(0x1b)&nbsp;string("[34~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F11:&nbsp;string(0x1b)&nbsp;string("[28~")&nbsp;\n&nbsp;\ 
 Shift&nbsp;&nbsp;&nbsp;&lt;Key&gt;F12:&nbsp;string(0x1b)&nbsp;string("[29~")&nbsp;\n&nbsp;\ 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Print:&nbsp;string(0x1b)&nbsp;string("[32~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Cancel:&nbsp;string(0x1b)&nbsp;string("[33~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Pause:&nbsp;string(0x1b)&nbsp;string("[34~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Insert:&nbsp;string(0x1b)&nbsp;string("[2~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Delete:&nbsp;string(0x1b)&nbsp;string("[3~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Home:&nbsp;string(0x1b)&nbsp;string("[1~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Prior:&nbsp;string(0x1b)&nbsp;string("[5~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Next:&nbsp;string(0x1b)&nbsp;string("[6~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;BackSpace:&nbsp;string(0x7f)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Num_Lock:&nbsp;string(0x1b)&nbsp;string("OP")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Divide:&nbsp;string(0x1b)&nbsp;string("Ol")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Multiply:&nbsp;string(0x1b)&nbsp;string("Om")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Subtract:&nbsp;string(0x1b)&nbsp;string("OS")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Add:&nbsp;string(0x1b)&nbsp;string("OM")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Enter:&nbsp;string(0x1b)&nbsp;string("OM")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Decimal:&nbsp;string(0x1b)&nbsp;string("On")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_0:&nbsp;string(0x1b)&nbsp;string("Op")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_1:&nbsp;string(0x1b)&nbsp;string("Oq")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_2:&nbsp;string(0x1b)&nbsp;string("Or")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_3:&nbsp;string(0x1b)&nbsp;string("Os")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_4:&nbsp;string(0x1b)&nbsp;string("Ot")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_5:&nbsp;string(0x1b)&nbsp;string("Ou")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_6:&nbsp;string(0x1b)&nbsp;string("Ov")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_7:&nbsp;string(0x1b)&nbsp;string("Ow")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_8:&nbsp;string(0x1b)&nbsp;string("Ox")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_9:&nbsp;string(0x1b)&nbsp;string("Oy")&nbsp;\n

&nbsp; 
 !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Up:&nbsp;string(0x1b)&nbsp;string("[A")&nbsp;\n\ 
 !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Down:&nbsp;string(0x1b)&nbsp;string("[B")&nbsp;\n\ 
 !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Right:&nbsp;string(0x1b)&nbsp;string("[C")&nbsp;\n\ 
 !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Left:&nbsp;string(0x1b)&nbsp;string("[D")&nbsp;\n\ 
 &nbsp; 
 *visualBell:&nbsp;&nbsp;&nbsp;&nbsp;true 
 *saveLines:&nbsp;&nbsp;&nbsp;&nbsp;1000 
 *cursesemul:&nbsp;&nbsp;&nbsp;&nbsp;true 
 *scrollKey:&nbsp;true 
 *scrollBar:&nbsp;true 
 
 </blockquote>

Note that real VT220 terminals use shifted function keys to
 mean something different: the user-programmable keys (i.e.,
 DECUDK). Modern xterm supports this, but the translations do not
 (they're using shift to select F13 to F20).

Here's another one, from Robert Ess
 &lt;ress@spd.dsccc.com&gt;:

#!/bin/sh 
 &nbsp; 
 #&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;vax

#&nbsp;09-17-96&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Bob&nbsp;Ess&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;initial&nbsp;creation

#&nbsp;09-26-96&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shig&nbsp;Katada&nbsp;&nbsp;-&nbsp;Additional&nbsp;keybindings

# 
 #&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Script&nbsp;file&nbsp;to&nbsp;incorporate&nbsp;keybindings&nbsp;and&nbsp;command&nbsp;line

#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;options&nbsp;for&nbsp;connecting&nbsp;to&nbsp;a&nbsp;VAX&nbsp;node

&nbsp; 
 #&nbsp;Usage&nbsp;statement 
 Usage(){ 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Usage&nbsp;&nbsp;:&nbsp;vax&nbsp;-options"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Options:&nbsp;-80&nbsp;&nbsp;&nbsp;for&nbsp;80&nbsp;column&nbsp;terminal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-132&nbsp;&nbsp;for&nbsp;132&nbsp;column&nbsp;terminal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-host&nbsp;[altair]&nbsp;[devel]&nbsp;[leonis]&nbsp;[castor]"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"" 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Example:&nbsp;\"vax&nbsp;-80&nbsp;-fg&nbsp;white&nbsp;-bg&nbsp;black&nbsp;-fn&nbsp;9x15&nbsp;-fb&nbsp;9x15b&nbsp;-host&nbsp;castor\""

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Starts&nbsp;a&nbsp;VAX&nbsp;session&nbsp;with&nbsp;an&nbsp;80&nbsp;column&nbsp;terminal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with&nbsp;a&nbsp;black&nbsp;background,&nbsp;white&nbsp;foreground,&nbsp;a&nbsp;normal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;font&nbsp;of&nbsp;9x15&nbsp;and&nbsp;a&nbsp;bold&nbsp;font&nbsp;of&nbsp;9x15b,&nbsp;and&nbsp;connects"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;If&nbsp;you&nbsp;need&nbsp;additional&nbsp;help,&nbsp;please&nbsp;call&nbsp;Workstation"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;exit&nbsp;1 
 } 
 &nbsp; 
 #&nbsp;Default&nbsp;to&nbsp;a&nbsp;black&nbsp;foreground&nbsp;with&nbsp;a&nbsp;white&nbsp;background.

#&nbsp;Use&nbsp;the&nbsp;9x15&nbsp;and&nbsp;9x15bold&nbsp;fonts.&nbsp;Connect&nbsp;to&nbsp;castor&nbsp;by&nbsp;default.

# 
 FG=black 
 BG=white 
 HOST=castor 
 FONT=9x15 
 BFONT=9x15bold 
 COLS=80 
 &nbsp; 
 #&nbsp;Parse&nbsp;the&nbsp;command&nbsp;line&nbsp;arguments

# 
 while&nbsp;[&nbsp;$#&nbsp;!=&nbsp;0&nbsp;]; 
 do 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;case&nbsp;$1&nbsp;in 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-80)&nbsp;&nbsp;&nbsp;&nbsp;COLS=80

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FONT=spc12x24c

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BFONT=spc12x24b

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-132)&nbsp;&nbsp;&nbsp;COLS=132

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FONT=9x15

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-fg)&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-bg)&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-fn)&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-fb)&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-host)&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-help)&nbsp;&nbsp;Usage;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;*)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Usage;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;esac 
 done 
 &nbsp; 
 xterm&nbsp;&nbsp;-title&nbsp;"VAX"&nbsp;-sb&nbsp;-sl&nbsp;1200&nbsp;-geo&nbsp;${COLS}x24&nbsp;-fg&nbsp;${FG}&nbsp;-bg&nbsp;${BG}&nbsp;\ 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-cr&nbsp;red&nbsp;-fn&nbsp;${FONT}&nbsp;-fb&nbsp;${BFONT}&nbsp;-xrm&nbsp;\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'XTerm*VT100.translations:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#override&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Insert:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(\001)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Up:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;scroll-back(1,lines)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Down:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;scroll-forw(1,lines)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Right:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("f")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Left:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("b")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Delete:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string(0x08)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Shift&nbsp;&lt;Key&gt;Tab:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("*")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF0D:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;scroll-back(1,page)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF0E:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;scroll-forw(1,page)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF09:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(\010)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF0A:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(\005)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;BackSpace:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0xff)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;Select:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-start()&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF02:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-end(PRIMARY,CUT_BUFFER0)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Meta&nbsp;&lt;Key&gt;0x1000FF02:&nbsp;&nbsp;&nbsp;select-end(CLIPBOARD)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;0x1000FF04:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;insert-selection(PRIMARY,CUT_BUFFER0)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Meta&nbsp;&lt;Key&gt;0x1000FF04:&nbsp;&nbsp;&nbsp;insert-selection(CLIPBOARD)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OP")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F2:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OQ")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F3:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OR")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F4:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OS")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F5:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OA")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F11:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("[23~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;F12:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("[24~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_0:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Op")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_1:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Oq")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_2:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Or")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_3:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Os")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_4:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Ot")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_5:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Ou")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Divide:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OP")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Multiply:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("[29~")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Enter:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("OM")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Subtract:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Om")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Add:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("Ol")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Key&gt;KP_Decimal:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string(0x1b)&nbsp;string("On")&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Btn1Down&gt;:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-start()&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Btn1Motion&gt;:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-extend()&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Btn1Up&gt;:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-end(PRIMARY,CUT_BUFFER0)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Button1&lt;Btn2Down&gt;:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;select-end(CLIPBOARD)&nbsp;\n\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Button1&lt;Btn2Up&gt;:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ignore()'&nbsp;\

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-e&nbsp;telnet&nbsp;$HOST&nbsp;&amp;

</blockquote>

Finally (for the moment) is a further modification of Robert
 Ess's script by <a href=
 "http://www-personal.une.edu.au/~oahlefel/">Erik Ahlefeldt</a>,
 &lt;oahlefel@metz.une.edu.au&gt;. From his readme file, for
 vmsterm:

<blockquote>
 This script is for people who wish to connect from a Linux
 or Unix computer to a VMS computer using telnet and get a good
 VT100 or VT220 emulation. The key mappings have been
 specifically designed to emulate the VT terminal auxiliary
 numeric keypad, so that you can use VMS EDT and TPU editors, as
 well as the many VMS applications use keys PF1 to PF4. The
 script should work with any recent version of Xterm using a
 standard extended IBM PC keyboard or a Sun keyboard.

About the keymappings. First the auxiliary numeric keypad.
 My prime objective with these mappings was to produce a setup
 that I could use with the EDT and TPU editors which make
 extensive use of the numeric keypad. The top row of keys PC
 numeric keypad (Num Lock, Divide, Multiply, Subtract) are where
 you find PF1, PF2, PF3, PF4 on a VT keyboard, so I have mapped
 them to PF1 thru PF4. The PC numeric keypad Add key (+) takes
 up the space of two keys which are Minus and Comma on the VT
 keyboard &ndash; I have mapped it to Comma (Delete Character in
 the EDT editor). I have then used the PC Pause key to map to VT
 key Minus (Delete Word in the EDT editor). The remaining keys
 on the auxiliary numeric keypad are the same for PC and VT.

The six keys between the main and numeric keypads on the PC
 (Insert, Home, Page Up, Delete End, Page Down) are usually
 mapped to the VT keys by either position or by (approximate)
 function. As I rarely use these keys I have mapped them by
 function as follows: PC key Insert to VT Insert Here, PC Home
 to VT Find, PC Page Up to VT Prev, PC Delete to VT Remove, PC
 End to VT Select, PC Page Down to VT Next.

<dl>
 <dt>Function keys.</dt>

<dd>
 There are 12 function keys on the PC keyboard and 20 on the
 VT keyboard, so I map PC F1 thru F12 to VT F1 thru F12
 (except for F1 thru F5 as noted below) and PC Shift F1 thru
 Shift F10 to VT F11 thru F20.

The VT keys F1 thru F5 are local hardware function keys
 so there is nothing to emulate, however some PC to VT
 emulations in the past have mapped PF1 thru PF4 here, so I
 have done that too, even though they are already mapped on
 the auxiliary numeric keypad.
 </dd>

<dt>Xterm functionality.</dt>

<dd>You lose some xterm functions when you remap the
 keyboard, however this script implements a scroll back buffer
 of 1000 lines which you scroll through using Shift and Up
 (a.k.a. Up Arrow or Cursor Up key) or Shift and Down.</dd>
 </dl>
 </blockquote>

a summary of the keyboard mapping:

<blockquote>
 <pre class="code-block">
PC Key maps to VT Key.
------ ------
F1 PF1
F2 PF2
F3 PF3
F4 PF4
F5 unused
F6 F6
F7 F7
F8 F8
F9 F9
F10 F10
F11 F11
F12 F12
Shift F1 F11
Shift F2 F12
Shift F3 F13
Shift F4 F14
Shift F5 F15 (Help)
Shift F6 F16 (Do)
Shift F7 F17
Shift F8 F18
Shift F9 F19
Shift F10 F20
Shift F11 F11
Shift F12 F12
Print Help (F15)
Cancel Do (F16)
Pause Keypad Minus

Insert               Insert Here
Delete               Remove
Home                 Find
End                  Select
Prior                Prev
Next                 Next
BackSpace            BackSpace (sends DEL - ascii 127)

Num_Lock PF1
KP_Divide PF2
KP_Multiply PF3
KP_Subtract PF4
KP_Add Keypad Comma
KP_Enter Enter
KP_Decimal Period
KP_0 Keypad 0
KP_1 Keypad 1
KP_2 Keypad 2
KP_3 Keypad 3
KP_4 Keypad 4
KP_5 Keypad 5
KP_6 Keypad 6
KP_7 Keypad 7
KP_8 Keypad 8
KP_9 Keypad 9
Up Up
Shift Up Scroll Back
Down Down
Shift Down Scroll Forward
Right Right
Left Left
</pre>
 </blockquote>

and the script:

#!/bin/sh 
 #&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;vmsterm

#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from&nbsp;an&nbsp;original&nbsp;script&nbsp;by&nbsp;Bob&nbsp;Ess

#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;key&nbsp;translations&nbsp;by&nbsp;Erik&nbsp;Ahlefeldt&nbsp;

# 
 #&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Script&nbsp;file&nbsp;using&nbsp;Xterm&nbsp;and&nbsp;telnet&nbsp;to&nbsp;connect&nbsp;to&nbsp;a&nbsp;VMS&nbsp;host

#&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and&nbsp;give&nbsp;a&nbsp;decent&nbsp;vt220&nbsp;emulation.

# 
 #&nbsp;Usage&nbsp;statement 
 Usage(){ 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Usage&nbsp;&nbsp;:&nbsp;vmsterm&nbsp;-options"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Options:&nbsp;-80&nbsp;&nbsp;&nbsp;for&nbsp;80&nbsp;column&nbsp;terminal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-host&nbsp;[crusher.saltmine.com]&nbsp;[earth]&nbsp;[192.168.7.7]"&nbsp;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"" 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Example:&nbsp;\"vmsterm&nbsp;-80&nbsp;-fg&nbsp;white&nbsp;-bg&nbsp;black&nbsp;-fn&nbsp;9x15&nbsp;-fb&nbsp;9x15b&nbsp;-host&nbsp;earth\""

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Starts&nbsp;a&nbsp;VMS&nbsp;session&nbsp;with&nbsp;an&nbsp;80&nbsp;column&nbsp;terminal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with&nbsp;a&nbsp;black&nbsp;background,&nbsp;white&nbsp;foreground,&nbsp;a&nbsp;normal"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;font&nbsp;of&nbsp;9x15&nbsp;and&nbsp;a&nbsp;bold&nbsp;font&nbsp;of&nbsp;9x15b,&nbsp;and&nbsp;connects"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Starts&nbsp;a&nbsp;VMS&nbsp;session&nbsp;with&nbsp;default&nbsp;terminal&nbsp;settings&nbsp;"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"" 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;Example:&nbsp;\"vmsterm&nbsp;-help\"" 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo&nbsp;"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Displays&nbsp;vmsterm&nbsp;options&nbsp;"

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;echo 
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;exit&nbsp;1 
 } 
 &nbsp; 
 #&nbsp;Default&nbsp;to&nbsp;a&nbsp;black&nbsp;foreground&nbsp;with&nbsp;a&nbsp;white&nbsp;background.

#&nbsp;Use&nbsp;the&nbsp;9x15&nbsp;and&nbsp;9x15bold&nbsp;fonts.&nbsp;Connect&nbsp;to&nbsp;192.168.3.3&nbsp;by&nbsp;default.

# 
 FG=black 
 BG=white 
 HOST=192.168.3.3 
 FONT=9x15 
 BFONT=9x15bold 
 COLS=80 
 &nbsp; 
 #&nbsp;Parse&nbsp;the&nbsp;command&nbsp;line&nbsp;arguments

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FONT=spc12x24c

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BFONT=spc12x24b

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;shift

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;;;

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;FONT=9x15

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BFONT=9x15b