.TH rxt L
.SH NAME
\*Lrxt \*O\(em Remote XTerm tool
.iX "rxt"
.SH SYNOPSIS
.sS
\*Lrxt host\*O
.sE
.SH AUTHOR
Craig DeForest zowie@mdisas.nascom.nasa.gov
.SH DESCRIPTION
\*Lrxt\*O
is a quick hack to avoid a lot of the B.S. that I dislike about
telnetting back and forth between systems in a distributed X 
environment.   
\*Lrxt\*O 
reads a database of the systems you like, the names
you like to call them by, and the characteristics you like to xterm them 
with.  Because I typically like to have a different color scheme
for every computer, but tend to change font and geometry to suit
my current task, rxt fires up an xterm with a specific set
of colors, depending on the host that you specify.
.PP 
\*Lrxt\*O
is best used when invoked *as* the host you want.  You can
link, eg, "myfavehost" to "rxt", and then typing "myfavehost" will
fire up an xterm on "myfavehost", with you favorite color scheme
and access mode (rsh or local sxterm with telnet).
.PP
You specify, in the database, whether rxt should try rsh'ing xterm
on the foreign host, or whether it should use a local xterm and then
telnet over there.  If you guess wrong and rsh doesn't work, 
rxt will use telnet.
.PP
If no database exists in your home directory,
\*Lrxt\*O
will insert one with my personal favorite hosts and color schemes.
You can modify the database with your favorite text editor -- it is
parsed by awk(1) and the fields are whitespace-delimited.
.SH FILES
.na
\*L~/.rxthosts\*O - contains the database.
.SH BUGS
I'm not sure what'll happen if more than one line in the database
matches your command-line host.  I think you'll get *two* windows
logged into the host.
.PP
If you specify a host that's not in the database, rxt does try
to invoke it with a default color scheme, but rxt does not 
add the host to the database.