# 1 "mterm.hlp"




'%@(#) Mterm help file 1.69.1.1\n























\node ,About mterm
{\lmargin +1em \bold \size 14
\section About mterm
}









    {\bold \ital mterm} runs on Data General AViiON hardware under DG/UX; 
    it requires a display device that runs the X Windows
    server.  You may run {\bold \ital mterm} on a server, with the X server
    running on an AViiON workstation.

\par
Like other UNIX programs, {\bold \ital mterm} responds to several 
command line options. See the topic entitled \link {Options, Options} 
for more information.  Because {\bold \ital mterm} is an X application,
it also supports X resources; see the topic entitled 
\link {X Resources, X Resources} for more information. 
\par
When using the {\bold \ital mterm} help facility, you can double click
on words that are underlined to view more information about the underlined
word/phrase. The topics underlined are called {\ital links,} and 
make it easy to find more information. For instance, below is a paragraph about
some of the chapters in this help document. To view any of these chapters,
simply double click on the desired {\ital link.} To return from a link to the 
help section you were in when the link was activated, press the {\bold Undo}
button. You may also go to the next or previous section by using the 
{\bold Next} or {\bold Previous} buttons.


The help facility provides information on the major {\bold \ital mterm}
\link {Features, Features}, as well as information on how to use 
{\bold \ital mterm.} The section on {\link {Command line options, Options}}
lists all the the command line options that can be used when starting 
{\bold \ital mterm.} The section on \link {X Resources, X Resources}
lists the {\bold \ital mterm} resources and some of the more popular X
resources.
These resources can be used to modify the look and actions of 
{\bold \ital mterm.}
Information on \link {Keyboard Mappings, Keyboard} is also available.
Part of terminal emulation is changing
the codes generated by the keyboard. This section lists information about
how the keyboard is remapped for each emulation mode. The \link 
{Search Facility, Search} is also discussed. {\bold \ital mterm} keeps lines
of text which have scrolled off of the screen in a special buffer called
history. 
You can view these lines by grabbing the vertical scroll bar and moving it up. 
The search facility allows you to search for text both on the visible part of 
the screen, and also back into the history buffer. This is very useful for 
viewing files and finding text.
  
\par
\vsp +4em
\par
\center {Mterm R4.20MU05 5.0}
\center {Copyright (C) Data General Corporation, 1990-1996}
\center {All Rights Reserved}
\par




\node ,Features
{\lmargin +1em \bold \size 14
\section Features
}

\break
\liststart
\item * 
D410 terminal emulation

\item *
Mapping of attributes to colors on workstations that support color.

\item *
The cursor row/column can be displayed as part of the window title.
See -cursorPos for more detail.

\item *
Macro language with single stepping

# 126 "mterm.hlp"


# 144 "mterm.hlp"


\item * 
Scrollable history.

\item * 
Select and paste (Cut and paste) is supported. Including select character,
select word, and select line. See the topic entitled \link {Mouse Support, Mouse Support} for more information.

\item * 
Sizable window. The {\bold \ital mterm} window is sizable 'on the fly'.

\item * 
Configurable menu. Can be used as a menu bar or a pop-up menu. Use the 
command line option -pm to get the pop-up menu (activated by button 3).
  
\item * 
If {\bold \ital mterm} is iconified and receives a command to beep the 
bell, the icon will reverse its video. This is most helpful 
for use with e-mail programs that ring the bell when new mail is received.
  
\item * 
Font size can be changed 'on the fly' using the {\bold \ital mterm} menu.
  
\item * 
A search facility is included. {\bold \ital mterm} will allow you to search
through the screen and history (saved lines) for text. Wild card characters
are supported. For more information see the \link {Search, Search} section.

\item * 
A complete \link {help, About mterm} system. The help system supports 
\link {links, About mterm} and a table of contents.

\item *
The ability to capture keystrokes and then play them back at the stroke
of a key.

\item *
You can save the contents of the screen or the history buffer to a file.
For more information see the \link {Save Screen, Save Screen} section.

\item *
\link {Printer Support, Printer Support}. mterm supports Print Screen, Print Window, 
and Print Form requests, as well as print pass-thru while in D410 or 
D216 mode. Print Screen support also is supported while in Vt100 mode.

# 200 "mterm.hlp"

\listend
\vsp +4em




\node ,Menu Items
{\lmargin +1em \bold \size 14
\section Menu Items
}

Main menu selections for {\bold \ital mterm} are File, View, Options, Async
and Help.

\par
{\bold File}
\par
\lmargin +4em
\liststart








\item Macros...
Selecting the \link {Macros...,Macros} item starts the macro menu which
allows you to start, single step, edit, and delete macros.

\item Logging...
When you select the \link {Logging...,Logging} item, 
{\bold \ital mterm} brings up a dialog box
that allows you to control logging functions.

\item Save Screen...
The \link {Save Screen..., Save Screen} option allows you to save the contents
of the screen and/or the \link {history buffer, About mterm} to a file.

\item File select...
The \link {File select..., File Select Box} entry will allow you to list your
files, and optionally
paste the selected file name into your mterm window. You may also cut from
the file selection box and paste into another window.

\item Exit
Exit {\bold \ital mterm}.
\listend
\lmargin -4em

{\bold View} 
\par
\lmargin +4em
\liststart
\item Search...
Use the \link {Search, Search} dialog box to enter a string or pattern to 
search for in history.
Indicate the direction of the search (forward or backward) and whether or
not the search should be case-sensitive.

\item Clear history
{\bold \ital mterm} keeps a copy of "terminal lines" that scroll off the 
terminal window; clearing the history area discards these saved lines. 

\item Clear all
This entry clears the history (see {\bold clear history} above) and clears the
screen. This is helpful when you display a file to
the terminal window. If you do a {\bold clear all} first, the screen and 
history
buffer will only contain the contents of the file, making it easy to use
the scroll bars to browse through the file.

\item Redraw
Use this selection to redisplay your terminal window.

\item Compose keys...
Display all the \link {international characters, Compose Keys} that can 
be used in {\bold \ital mterm}. 

\item Toggle video
Use this selection to exchange the screen's foreground and background
colors; on monochrome displays, this exchange is the same as reversing the
video attributes of the screen.

\item Toggle Display of Cursor Position
Use this selection to display or not display the cursor row/column position
as part of the window title.

\item Scroll mode
{\bold \ital mterm} will either scroll the screen smoothly or in line-sized 
jumps; use
this selection to set your preference.

\listend
\lmargin -4em

\par
{\bold Options}
\par
\lmargin +4em
Items on the options menu allow you to specify your preferences for the 
current {\bold \ital mterm} session. These changes are not saved.
\liststart

\item Bell...
When {\bold \ital mterm} receives a terminal code to ring the bell, it will 
respond in one
of three ways - sound the workstation bell, flash the screen, or both.
\item History...
Specify how many lines you want saved in history and/or whether to
save the whole screen when {\bold \ital mterm} receives a "clear
screen" control code.
\item Titles...
Specify the {\bold \ital mterm} window title and icon name.
# 333 "mterm.hlp"

\item Font size
Select a new font size.
\item Color...
Displays the \link {Color,Color} Set editor screen. This allows you to 
modify the colors used by mterm when displaying text. This feature is only 
available if you have a color monitor.
\item Newline
Set the value of the <Enter> key.
\item Backspace
Set the value of the Backspace key
\listend
\lmargin -4em

\par
{\bold Async}
\par
\lmargin +4em
The Async menu selection allows you to change baud, word length, parity, flow control
and stop bits for your current async session. You can also view the modem status, determine
whether the high bit should be stripped, send a break, a hang up the modem.This menu
item is desensitized when mterm is not in async mode. 
\lmargin -4em

\par
{\bold Help}
\par
\lmargin +4em
When you select this menu item, {\bold \ital mterm} brings up a help
window.  The help window allows you to view help information about 
{\bold \ital mterm.}  It is what you are doing now.
\lmargin -4em
\par
\vsp +4em




\node ,Options
{\lmargin +1em \bold \size 14
\section Options
}
{\bold \ital mterm} responds to several command line options.  The table 
below lists all of these options and the setting that {\bold \ital mterm}
uses by default.
\vsp +4em
\lmargin +4em
\liststart

\item {\bold Mterm option \norm}
{\bold Description:}

\item {\bold Async options}
\break

\item -7bit               
Set the word length to 7 bits. The compose menu and the compose key do not
function in 7 bit mode. Only international characters on your keyboard can
be generated.

\item -8bit               
Set the word length to 8 bits - this is the default. In 8 bit mode the compose
menu and the compose key are available. All international characters can be
generated. [default]

# 426 "mterm.hlp"


\item {\bold Bell options}
\break

\item -ab
Turn audible bell on. [default] 

\item +ab
Turn audible bell off.

\item -bc COUNT 
Set number of beeps/flashes for bell. [1] 

\item -vb                 
Turn visual bell on.        

\item +vb                 
Turn visual bell off. [default] 



\item {\bold Emulator options}
\break

# 462 "mterm.hlp"


\item -nl VALUE [cr]
Define your <Enter> key to be cr, nl, or crnl.

\item -bs VALUE [bs]
Define backspace to be bs (backspace) or delete. This option only
determines what code is sent when the key is pressed, it does not
do an stty setting like -backspace does.

\item -strip
Strip the high bit.

\item +strip
Don't strip the high bit.

\item -d410mid CODE 
Set the D410 model id code returned in DG mode.

# 499 "mterm.hlp"


\item -ah
Allow the window to scroll horizontally to keep the cursor displayed.
[default]

\item +ah
Do not scroll the window horizontally to keep the cursor displayed.

\item -ic
When in d410 mode, {\bold \ital mterm} will normally change the window size
to 24x135 when it receives a command to go to compressed mode. This allows
all of the charcters to be displayed. The -ic (ignoreCompress) option
tells mterm to ignore the requests to change between compressed and normal
modes. 

\item +ic
Allow mterm to recognize requests to change between compressed and normal
modes. [default]

\item -ss
Do horizontal and vertical scrolling in smooth scroll mode.

\item +ss
Do horizontal and vertical scrolling in jump scroll mode.
[default]

\listend



{\bold Font name options}

{\bold WARNING:} All fonts specified should be the same size in order to
get predictable behavior from the emulator. Any fonts different from
sizes 8, 10, 12, 14, 18 or 24 will not work correctly in a D410.
\liststart
\item -bf FONT
Define the bold font. If no bold font is specified, the default bold font 
will be used. If an invalid bold font is specified, the dim font will be used.
An example of a bold font is:\break
-adobe-courier-bold-r-normal--18-180-75-75-m-110-iso8859-1

\item -bbf FONT
Define the bold blink font. If no bold blink font is specified, the 
default bold blink font will be used. If an invalid bold blink font is
specified, the bold font will be used. An example of a bold blink font is:
\break
-adobe-courier-bold-o-normal--8-80-75-75-m-50-iso8859-1

\item -blinkFont FONT
Define the blink font. If no blink font is specified, the default
blink font will be used. If an invalid blink font is specified, the
dim font will be used. An example of an blink font is:
-adobe-courier-medium-o-normal--12-120-75-75-m-70-iso8859-1

\item -df FONT
Define the dim font. If no dim font is specified, the 
default dim font will be used. If an invalid dim font is specified, 
{\bold \ital mterm} exits with an appropriate error message. An example of
a dim font is:
\break
-adobe-courier-medium-r-normal--14-140-75-75-m-90-iso8859-1
\listend


{\bold Font template options}

{\bold WARNING:} We do not recommend using any of these options except 
to set the font size; most users will want to use the default fonts or 
the font name options instead. These options CANNOT be used with any of 
the font name options or resources (e.g. -df or *dimFont). 

{\bold \ital mterm} provides the following 6 font options to allow a
user to specify a font by setting parts of the name instead of a
complete font name. You can set any combination of font template options
resulting in a valid font name. For example, if you just want to set the
font size of the default font to 18, enter {\bold mterm -fs 18.} This
will NOT work if any of the font name resources have been set.

As an example of which parts in a font name can be set, in the font 
 -adobe-courier-medium-r-normal--14-140-75-75-m-90-iso8859-1,\break
the font maker is adobe, the font family is courier, the font size is
14, the font dpi is 75, the font width is 90, and the font character set 
is iso8859-1.
\break

\liststart
\item -fc CHAR_SET
Set font character set (e.g. iso8859-1). [*]
\break
{\bold WARNING:} This option will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item -fd DPI
Set font dpi (i.e. dots per inch, usually 75 or 100).  [*]
\break
{\bold WARNING:} This option will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item -ff FAMILY
Set font family (e.g. courier, times or helvetica). [courier]
\break
{\bold WARNING:} This option will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item -fm MAKER
Set font maker (e.g. adobe, dec or sun).  [*]
\break
{\bold WARNING:} This option will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item -fs SIZE            
Size of font from the following list:\break
{8, 10, 12, 14, 18, 24}   [14]
\break
{\bold WARNING:} If you have specified font names you must set the
font size to the correct value. If the font size does not match the 
specified fonts, characters will be displayed incorrectly.

\item -fw WIDTH
Set font width (i.e. the mean width of all glyphs in the font).    [*] 
\break
{\bold WARNING:} This option will NOT work if any of the font name
resources have been set - use only with the default fonts.



\item {\bold History options}
\break

\item -sc                 
Save cleared screens to the history buffer.

\item +sc                 
Don't save cleared screens. [default]

\item -sl SAVE_LINES
Number of history lines saved. [100]



\item {\bold Logfile options}
\break

\item -lf FILENAME
Name of log file. This file is used by the Logging feature of mterm.
[$HOME/mterm.log]

\item -logging            
Record {\bold \ital mterm} session in logfile.  
WARNING: Be sure to stop logging before displaying the logfile to the screen. 
If you display the logfile to the screen while logging, you will 
create an endless loop of displaying from the log what was written to
the screen and then written to the log....

\item +logging            
Don't record {\bold \ital mterm} session. [default] 

\item -sf FILENAME
This option allows you to define the default file that will be used when
using the Save Screen feature of mterm. For information on the difference
between Save Screen and Logging please see \link {Save Screen, Save Screen}.

\item {\bold Window options}
\break

\item -bg COLOR
Set background color. [white]

\item -colorSet COLOR_SET
Map attributes to colors. This switch should only be used on color
workstations. The $HOME/.mtermrc resource file contains up to 20 
color sets that can be used to map attributes to colors.
The list of available color sets can be used by using the 'Color...'
option from the 'Options' menu. No color sets are shipped with mterm.
You must create them before using the -colorSet command line option. For the
color editor to be available on 24 bit systems you must start X11 with the
-cc 3 command line option. The X11 command line can be found in the
/var/X11/xdm/Xservers file.

\item -fg COLOR
Set foreground color. [black]

# 691 "mterm.hlp"


\item -geometry CxR+X+Y
<columns>x<rows>[+-]<xoff>[+-]<yoff>  [80x24+0+0 or 81x24+0+0]

\item -iconic             
Start as an icon.

\item -in ICONNAME
Set icon name.  [mterm]

\item -name NAME          
Define instance name. Also defines default
window title and icon name.   [mterm]

\item -pm
Use a pop-up menu instead of a menu bar.

\item +pm
Use menu bar instead of pop-up menu.  [default]

\item -title WINDOWNAME   
Set window title.    [mterm]



\item {\bold Other options}
\break






\item -mp
Define the directory where your macro files are located.

\item -cursorPos or -cp
Display the current cursor row and column position as part of the 
window menu title. When using this option the window title will be
truncated to 256 characters to make room for the row/column information.
This feature is off by default.

\item +cursorPos or +cp
Turn the display of the current cursor row and column position off.
This is the default.

\item -pc CMD_LINE
Define the print command for print pass through, Print Screen, Print Form, and Print Window.
The argument must be quoted if it contains spaces.

\item -xrDebug
Output debugging information on the resource
file.
NOTE: This option is intended for 
development purposes and NOT for users. 

\item +xrDebug
Turn resource debugging off. [default] 

\item -debug
Output debugging information and record keypresses when logging. 
NOTE: This option is intended for 
development purposes and NOT for users. 

\item +debug
Turn debugging off. [default] 

# 769 "mterm.hlp"


\item -sd NUMBER
Set the delay in smooth scrolling at the end of a line to be
NUMBER in hundredths of a second.

\item -uk KEY_MAP
Use KEY_MAP to redefine the keyboard. KEY_MAP is a resource in one of the
resource files. The format is standard translation table format.
More information can be found in Chapter 7 of the {\ital X Toolkit Intrinsics
Programming Manual} for X Version 11.

\item -ut                 
Make utmp entry. [default]

\item +ut                 
Don't make utmp entry.

\item -version
Version string.

\item -xrm "RESOURCE:VALUE"
Set a resource value from the command line. See the 'X' manpage for more
information about the -xrm commandline option.

\listend
\lmargin -4em
\vsp +4em




\node ,X Resources
{\lmargin +1em \bold \size 14
\section X Resources
}

The table below names resources that are specific to {\bold \ital mterm}
 and what value
{\bold \ital mterm} uses for each if you do not set the value yourself.
\vsp +4em
\lmargin +4em
\liststart
\item \bold Mterm*RESOURCE: DEFAULT \norm     

\bold Description:\norm 

\item {\bold Async Resources:}
\break
# 845 "mterm.hlp"


\item Mterm.wordLength: 8bit       
Word length {7bit, 8bit}.
Set the word length to 7 or 8 bits. The compose menu and the compose key do
not function in 7 bit mode. Only international characters on your keyboard
can be generated when in 7 bit mode. In 8 bit mode the compose menu and the 
compose key are available. All international characters can be generated.
The default is 8 bit mode.




\item {\bold Bell resources:}
\break

\item Mterm.audibleBell: true      
If true, make bell signal audibly (beep).

\item Mterm.bellCount:  1          
Set number of beeps and/or
flashes of the bell {0-9.}

\item Mterm.visualBell: false      
If true, make bell signal visually (flash).




\item {\bold Emulation mode resources:}
\break

\item Mterm.allowHScroll: true
Allow mterm to scroll the screen horizontally to keep the cursor displayed.






\item Mterm.nl: cr
Set the character(s) to be sent when the <Enter> key is
pressed. The valid entries are cr, nl, and crnl.

\item Mterm.bs: bs
Set the value fo the backspace character to either bs or delete.

\item Mterm.strip: false
Strip the high bit, turning 8 bit characters into 7 bit
characters.

\item Mterm.d410ModelId:
Set the D410 model id code returned when in DG mode.

# 911 "mterm.hlp"


\item Mterm.ignoreCompress: false
When in d410 mode, {\bold \ital mterm} will normally change the window size
to 24x135 when it receives a command to go to compressed mode. This allows
all of the charcters to be displayed. The -ic (ignoreCompress) option
tells mterm to ignore the requests to change between compressed and normal
modes. 

\listend




{\bold Font name resources:}
 
{\bold WARNING:} All fonts specified should be the same size in order to
get predictable behavior from the emulator. Any fonts different from
sizes 8, 10, 12, 14, 18 or 24 will not work correctly in a D410.

\liststart
\item Mterm.boldFont: 
Define the bold font. If no bold font is specified, the default bold font
will be used. If an invalid bold font is specified, the dim font will be used.
An example of a bold font is:
-adobe-courier-bold-r-normal--18-180-75-75-m-110-iso8859-1

\item Mterm.boldBlinkFont: 
Define the bold blink font.  If no bold blink font is specified, the
default bold blink font will be used. If an invalid bold blink font is
specified, the bold font will be used. An example of a bold blink font is:
-adobe-courier-bold-o-normal--8-80-75-75-m-50-iso8859-1

\item Mterm.blinkFont:
Define the blink font.  If no blink font is specified, the default
blink font will be used. If an invalid blink font is specified, the
dim font will be used. An example of an blink font is:
-adobe-courier-medium-o-normal--12-120-75-75-m-70-iso8859-1

\item Mterm.dimFont:
Define the dim font.  If no dim font is specified, the
default dim font will be used. If an invalid dim font is specified,
{\bold \ital mterm} exits with an appropriate error message. An example of 
a dim font is:
-adobe-courier-medium-r-normal--14-140-75-75-m-90-iso8859-1
\listend



{\bold Font template resources:}
 
{\bold WARNING:} We do not recommend using any of these resources except
to set the font size; most users will want to use the default fonts or
the font name resources instead. These resources CANNOT be used with any of
the font name options or resources (e.g. -df or .dimFont).

{\bold \ital mterm} provides the following 6 font resources to allow a
user to specify a font by setting parts of the name instead of a
complete font name. You can set any combination of font template resources
resulting in a valid font name. For example, if you just want to set the
font size of the default font to 18, put {\bold Mterm.fontSize: 18}
in your .Xdefaults file. This will NOT work if any of the font name 
resources have been set.
 
As an example of which parts in a font name can be set, in the font
 -adobe-courier-medium-r-normal--14-140-75-75-m-90-iso8859-1,\break
the font maker is adobe, the font family is courier, the font size is
14, the font dpi is 75, the font width is 90, and the font character set
is iso8859-1.

\liststart
\item Mterm.fontCharset:
Set the font character set (e.g. iso8859-1).
\break
{\bold WARNING:} This resource will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item Mterm.fontDpi:     *         
Set the font dpi (i.e. dots per inch, usually 75 or 100).
\break
{\bold WARNING:} This resource will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item Mterm.fontFamily: courier    
Set the font family (e.g. courier, times or helvetica).
\break
{\bold WARNING:} This resource will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item Mterm.fontMaker:   *         
Set the font maker (e.g. adobe, dec or sun).
\break
{\bold WARNING:} This resource will NOT work if any of the font name
resources have been set - use only with the default fonts.

\item Mterm.fontSize: 14           
Size of font from the list
{8, 10, 12, 14, 18, 24.}
\break
{\bold WARNING:} If you have specified font names you must set the
font size to the correct value. If the font size does not match the 
specified fonts, characters will be displayed incorrectly.

\item Mterm.fontWidth:   *         
Set the font width (i.e. the mean width of all glyphs in the font).
\break
{\bold WARNING:} This resource will NOT work if any of the font name
resources have been set - use only with the default fonts.
\listend



\liststart
\item {\bold History resources:}
\break

\item Mterm.saveCleared: false     
Save cleared screens if true.

\item Mterm.saveLines: 100         
Number of saved lines of history.
\listend



\liststart
\item {\bold Logfile resources:}
\break

\item Mterm.logfile: $HOME/mterm.log
Name of log file, when logging.

\item Mterm.logging: false         
If true, log the {\bold \ital mterm} session.
WARNING: Be sure to 
stop logging before displaying the logfile to the screen. If you
display the logfile to the screen while logging, you will 
create an endless loop of displaying from the log what was written to
the screen and then written to the log....

\item Mterm.saveFile: $HOME/mterm.scrn
Name of the Save Screen file. Please see \link {Save Screen, Save Screen} for
more information about the difference between the logfile and the save screen
file.

\listend




# 1072 "mterm.hlp"



\liststart
\item {\bold Window resources:}
\break

\item Mterm*background: White      
Background color.

\item Mterm.colorSet: name
Mterm will use the defined color set to map display attributes such as 
bold, blink, underline and reverse to be displayed in color. No defaults
color sets are supplied with Mterm. You must use the Color Set Editor
and create one or more color sets before using this option.
For the
color editor to be available on 24 bit systems you must start X11 with the
-cc 3 command line option. The X11 command line can be found in the
/var/X11/xdm/Xservers file.

\item Mterm*foreground: Black      
Foreground color.







\item Mterm.geometry:
Geometry string with format
<columns>x<rows>[+-]<xoff>[+-]<yoff>. Please note
the use of the '.' instead of the normal '*' after
the classname (Mterm). This is necessary to allow 
the help windows to be properly sized. the default for
vt100 and d216 is 80x24+0+0. The default for d410 is
81x24+0+0.

\item Mterm.iconName: mterm        
Set icon name.

\item Mterm.iconPixmap: mterm_icon        
Set bitmap to use for icon.







\item Mterm.title:    mterm        
Set window title.

\item Mterm*scrollBarPlacement:
Place horizontal scroll bar at the
bottom of the window and vertical
scroll bar to the right. Horizontal
scroll bar placement can be TOP or
BOTTOM; vertical scroll bar placement
can be LEFT or RIGHT. The default setting
is BOTTOM_RIGHT

\listend



\liststart
\item {\bold Other resources:}
\break







\item Mterm.macroPath: 
This resource defines where your macro files are located. The
default is .mtermMacros in your home directory. ~ and
$HOME are not supported in this pathname.

\item Mterm.xrDebug:   false         
If true, turn on resource file
debugging.For development purposes ONLY.

\item Mterm.debug:   false         
If true, turn on debugging.
For development purposes ONLY.









\item Mterm*mouseCursor:	center_ptr
Use the specified cursor inside the {\bold \ital mterm} text area. 
Valid entries include: any of the standard cursor shapes listed in 
the <X11/cursorfont.h> file (minus the XC_ prefix), a bitmap file name, 
or a font name and glyph index.

\item Mterm.popupMenu:  false
If true, use a popup menu instead of a menu bar to display menus.

\item Mterm*reverseVideo: off      
Control reverse video.
This X resource doesn't work;
use *background:black instead.

\item Mterm.scrollDelay:  0
Delay (in hundredths of a second) in smooth scroll at the end of a line.

\item Mterm.smoothScroll: false
If true, smooth scrolling will be used;
else jump scrolling will be used.

\item Mterm.userKeymap: NULL
Define which user defined keymap to use. The keymap is a resource in the
users .Xdefaults file. The format is standard translation table format.
More information can be found in Chapter 7 of the {\ital X Toolkit Intrinsics
Programming Manual} for X Version 11.

\item Mterm.utmpInhibit: false     
Make utmp entry if false.

\listend
\lmargin -4em 
\vsp +4em




\node ,Mouse Support
{\lmargin +1em \bold \size 14
\section Mouse Support
}
\liststart
\item Select by drag: Press B1 and move mouse.
\item Select by word: Double click B1.
\item Select by line: Triple click B1.
\item Paste: Single click B2.
\item Strip control characters and paste: <CTRL> B2.

\listend
Note: Your mouse may support other functions as determined by your
window manager.




\node ,Keyboard
{\lmargin +1em \bold \size 14
\section Keyboard
}
\par 
{\bold \ital mterm} remaps the Aviion keyboard to duplicate as closely as
possible the terminal being emulated. In addition, you can redefine 
keys to match your own individual needs by using the userKeymap resource
or the -uk command line option. You can also capture keystrokes by pressing
<CTRL><INSERT>. Type <CTRL><INSERT> again to terminate keystroke capture. Up
to 128 keystrokes will be recorded. You can play back the recorded keystrokes
by pressing <ALT><INSERT>. The bell will beep once when starting capture, and
twice when terminating capture. <SHFT><ALT><INSERT> will paste the current
cut  buffer contents. <CTRL><ALT><INSERT> will paste the current
cut  buffer contents, but strip all control characters and turn NLs and TABs
to spaces. You can also use your \link {mouse, Mouse Support} for pasting.

\par
The AViiON keyboard differs from the keyboard of the Data General Corporation
D series of terminals. The following
table displays which AViiON key may be used to emulate a specific 
D series keys.

\lmargin +8em
\liststart
\item {\bold D216/D410 key}
AViiON key \norm

\item C1          
Insert

\item C2          
PgUp

\item C3          
Delete

\item C4          
PgDn

\item Home        
Home or <CTRL>H

\item Erase EOL 
End or <CTRL>K

\item Erase Page
<ALT>End or <CRTL>L 

\item Spcl
Pause

\item CR (Carriage Return)
<CTRL><ENTER>

\listend
\lmargin -8em

\par
Note that shifted versions of C1-C4 are also supported.

\par
 Function keys 11 thru 15 are available as ALT-F1 thru
 ALT-F5 provided your window manager does not intercept these keys.
 If you are having trouble with generating F11 thru F15, please refer
 to the WARNINGS section of the mterm manpage. All shift and control 
 combinations are supported.
 Mterm also supports a Clear All function on <Alt><Return>.
 Pressing <Alt><Return> clears the screen and the history
 buffer, and then sends out the normal <Enter> key.

\par
To generate a break condition, press <ALT><B> or <ALT><b>. The default
break duration is set to 0, which uses the system defaults.
The break duration can be changed
by the -bd command line option or the breakDuration resource.
The argument represents tenths of a second.

\par
While in D216 or D410 mode you may do a Print Form by pressing 
<Ctrl><Print Screen>. A Print Window request can be generated by pressing 
<Shift><Print Screen>. The <Print Screen> key prints all of the dispayed {\bold \ital mterm} window in both
DGC and Vt100 modes. For more information see the \link {Printer Support, Printer Support}
section.


\lmargin -8em



# 1365 "mterm.hlp"


\par

More information about keyboard mapping can be found in:

\center  {/usr/lib/X11/app-defaults/Mterm.}

\vsp +4em

\node ,Color
{\lmargin +1em \bold \size 14
\section Color
}
The 'Color...' menu item on the 'Options' menu will start the Color Set
Editor. The Color Set Editor (CSE) allows you to define up to 20 different
colors sets. Each color set maps attributes such as bold, to a specific 
foreground/background color. To use CSE select foreground or background, 
and which attribute you want to set the color for. 
You then have 4 ways to select the color. You may use the mouse
and 'pick' a color from the color chart; you may select a color from the
list of colors in the selction box; you may type in the name or RGB value 
of a color; and you may use the RGB sliders to generate a color. When using
the sliders, the closest named color is always displayed in the color name
field. The color of the selected attribute will change as you make color
selections. 
If you 'double click' on an attribute, its color will be highlighted
in the selection box. The 'Grab Color' button turns the cursor to a cross
hair and allows you to select a color anywhere on the screen. The 
'Grab Attribute' button puts a cross hair cursor in the mterm window. You
then click on the character whose attribute you want to change.
If you use RGB values or the sliders to generate a color, the closest
named color will be used. Using named colors decreases the
chance of running out of color cells. Once you have the attributes mapped
to the desired colors you should save that color set if you want to use it
in the future. Once you have created a color set, you can use 
'-colorSet name' when starting mterm to define which
color set to use. You may also use the Mterm.colorSet resource. NOTE:
For the
color editor to be available on 24 bit systems you must start X11 with the
-cc 3 command line option. The X11 command line can be found in the
/var/X11/xdm/Xservers file.



\vsp +4em

\node ,Compose Keys
{\lmargin +1em \bold \size 14
\section Compose Keys
}
In 8-bit mode, {\bold \ital mterm} lets you generate international
characters from any keyboard.
Two international character sets can be displayed.
In VT100 and VT52 mode, Latin Alphabet No. 1 (ISO 8859-1) is supported.
In D2l6 and D410 mode, the Data General International (DGI) character set
is supported.

One way to generate international characters is to use a three-key sequence
known as a compose sequence.
First, press the compose key, then press two other keys.
The default compose key on the AViiON keyboard is the {\bold \ital Pause} key,
located at the upper right corner of the keyboard.
To see what two other keys to press, select Compose Keys from the
{\bold \ital View} menu.
A Compose menu will be displayed containing buttons labeled with each
character and the two keys used to generate it from the keyboard.
The two-key sequence can be typed in either order;
for example, to generate , press <Pause><A><E> or <Pause><E><A>.

An alternate way to generate an international character in your
{\bold \ital mterm} window is to select the Compose Keys menu item and
then click your mouse on the button representing the character you
want.
Only Latin 1 characters are displayed.

If a character specified by a compose sequence or selected by mouse
is not valid for the current emulation mode, the character will not
be generated.
The Compose menu includes only Latin 1 characters, many of which are
also DGI characters.

\node ,Environment
{\lmargin +1em \bold \size 14
\section Environment
}
The following table enumerates the UNIX shell environment variables used by 
{\bold \ital mterm.}
\lmargin +8em
\par
\liststart
\item KBD_LANG 
Valid entries for {\bold \ital mterm} are:
KBD (Keyboard), US, UK, ,USENGLISH, UKENGLISH, FRENCH, GERMAN, SWEDISH,
SPANISH, DANISH, SWISS, FINNISH, FRENCH_CANADIAN, NORWEGIAN, PORTUGUESE,
and ITALIAN. This variable only needs to be set
if you are running {\bold \ital mterm} from a host other than
your workstation and your keyboard language is
not US.

\item XUSERFILESEARCHPATH
We recommend using XUSERFILESEARCHPATH.
(See X(1) for more information.)

\item XHELPPATH
You can use XHELPPATH to force mterm to use a different directory for
locating the help files.
If XHELPPATH is not set, mterm uses /usr/opt/X11/xhelp/C/Mterm







\item HOME            
Determines where the default logfile will be
created.

\listend 
\lmargin -8em
\vsp +4em




\node ,Logging
{\lmargin +1em \bold \size 14
\section Logging
}
{\bold \ital mterm} will maintain a log of all characters it receives if 
logging is turned on using the -logging command line option or if .logging
was set to True. When logging,
{\bold \ital mterm} writes characters to a file as well as to the screen.
You control whether {\bold \ital mterm} logs characters; further,
you control the name and pathname of the log file. 
\par
WARNING: Be sure to 
stop logging before displaying the logfile to the screen. If you
display the logfile to the screen while logging, you will 
create an endless loop of displaying from the log what was written to
the screen and then written to the log....
 
\par
Logging behavior may be specified by changing settings in the Logging dialog
box.  You bring the dialog box up by selecting the Logging item in the File
menu.
\par
By default, {\bold \ital mterm} uses $HOME/mterm.log for its log file.
To change the name of your log file, enter the new file name in the Logfile 
Name text area any time prior to selection of 'Start'. 
Clicking on the 'append' button
or the 'overwrite' button followed by selection of 'Start' starts logging to
the file named in the text area.
If the 'append' button is highlighted,
logging either appends to an old file or starts a new log if the named file 
has not yet been created. If the 'overwrite' button is highlighted,
logging either creates a new file or overwrites any information previously 
written to an existing file. Selection of 'Stop' discontinues logging,
'Close' exits from the dialog box, and 'Help' displays information about the
Logging dialog box.
\par
If you want to take a 'snapshot' of what is on the screen or in the history
buffer you can use the \link {Save Screen, Save Screen} feature.
\vsp +4em




\node ,Macros
{\lmargin +1em \bold \size 14
\section Macros
}
Macros (scripts) allow you to define keystrokes you want to be sent as if
typed from the keyboard. The {\bold \ital mterm} macro facility also lets
you monitor what is being received into the emulator to determine what
should be sent. There are also messaging commands to provide information
to the user, and the send command allows for input to be taken from the
user and included in the data being 'typed' by the macro.
\par
The macro menu lists the macros installed in your macro directory, which
by default is ~/.mtermMacros. The macro directory can defined using the
-mp command line option or the .macroPath resource. 
The contents of each  macro can be displayed
by clicking on the desired macro. Macros may be run or single stepped,
and be started or continued on any line by selecting the line and then
pressing 'Run' or 'Next'. Macros can be edited by pressing the 'Edit'
button, which starts the xedit program and loads the selected macro for
editing. See the xedit manpage for infomration on how to use xedit.
\par
Macro commands can be in upper or lower case and must start in the first
column.
\par
{\bold Macro Commands:}

\liststart
\item {done}
Terminate macro execution and close macro widget.

\item {goto} LABEL
Continue execution at first line after LABEL

\item {break}
stop the macro that is currently executing. Execution may be resumed from
the current location by pressing 'Next' or 'Run'. Execution may be resumed
at an alternate line by first selecting the desired line, and then pressing
'Next' or 'Run'. 'Next' executes the next line and then stops. 'Run'
executes until the end of the macro is reached, the command 'done' is
encountered, or 'Stop' is pressed.

\item {wait} SECONDS
Wait SECONDS and then continue execution with the next line.

\item {wait} SECONDS,SEARCH_STRING
wait for upto SECONDS for the SEARCH_STRING to be received form the child
process (the child process can be a modem, an async connection to another
system, or a local shell process such as csh). When the time elapses or the 
string is received, macro execution will continue on the next line.

\item {wait} SECONDS,SEARCH_STRING,LABEL,...
wait for upto SECONDS for the SEARCH_STRING to be received form the child
process (the child process can be a modem, an async connection to another
system, or a local shell process such as csh). If time elapses, macro 
execution will continue on the next line. If a SEARCH_STRING is matched,
execution will continue at LABEL. If the last
search string is matched and there is no label for it, macro execution
will continue on the next line.

\item {message} STRING
Display a message in a popup window. Users clears by pressing OK.

\item {working} STRING
Clears any existing working message and then displays the new working message.

\item {working}
Clears last working message.

\item {error} STRING
Display an error message in a popup window. Users clears by pressing OK.

\item {warning} STRING
Display a warning message in a popup window. Users clears by pressing OK.

\item {send} STRING
send a string of text as if typed from the keyboard. Use of
'#xx#' escape sequences is supported. The user will be prompted
for input if a ^ sign is found. Anything from the ^ to the next
^ will be used as a prompt for user input. If the second ^ is
not found, the ^ will be sent as a ^ and no user input will be
requested. If you don't want the input echoed, use $ instead of ^
to mark the prompt for the input request. 

\item {title} TITLE
Set the mterm window and icon title to TITLE. Input prompts and character
escape sequences are supported as in the 'send' command.

\item {exec} COMMANDLINE
Mterm treats COMMANDLINE much the same way a shell does: the first word in
COMMANDLINE is used as the executable to start, and the rest are used as the
arguments for the executable. Mterm does a fork and then uses execvp to start
the requested command. This feature could be used to use the macro list like
a menu system.










\listend
\par
#xx# escape sequence information:
\par
The string is scanned to find a '#nn#' sequence.
If a # sequence is found, the token betwenn the two # signs
is referenced against an array of control code mnemonics. If a
match is found the '#nn#' sequence is replaced by a single byte
of the value of the control sequence mnemonic. If a match is not
made, the token will be treated as a hex string and converted 
from it's ascii string representation to control character. If
the token is not a valid hex string, the token will be printed
as a normal text string. 
\par
The following control code mnemonics can be used to represent the
control codes 0 thru 31:
\par
"NULL","SOH","STX","ETX","EOT","ENQ","ACK","BELL","BS",
"TAB","NL","VT","FF","CR","SO","SI","DLE","DC1","DC2","DC3",
"DC4","NAK","SYN","ETB","CAN","EM","SUB","ESC","FS","GS",
"RS","US","DEL"
\par
The following control code symbols can also be used:
\par
"^@","^A","^B","^C","^D","^E","^F","^G","^H","^I","^J",
"^K","^L","^M","^N","^O","^P","^Q","^R","^S","^T","^U",
"^V","^W","^X","^Y","^Z","^[","^\\","^]","^^","^_"
\par
Examples:
\par
send ^Username: ^#NL#
\par
send $Password: $#^J#
\par
Would prompt the user for their username and would then send it followed by
a newline. The user would then be asked for their password, which would not
be echoed as it was typed. The password would then be sent to the child
process followed by a newline.


\node ,Save Screen
{\lmargin +1em \bold \size 14
\section Save Screen
}
Save Screen allows you to take a snapshot of what is displayed in your mterm 
screen and/or what is in your history buffer, and save it to a file. You may
append or create the file. If append is selected, the file will be created if
it does not already exist. If create is selected, the file will be deleted if 
it already exists, and then created.

Using Save Screen is different than logging. When logging is started it is a 
continous  activity that takes place while you are using mterm. Logging
saves to a file all ASCII text received by mterm, for as long as
logging is enabled. Save Screen allows you to take a snapshot of what is
displayed in your mterm screen and/or what is in your history buffer, and
save it to a file. The log file will not always save what your screens 
actually looked like because the screen may not have been drawn top to
bottom.

\node ,Printer Support
{\lmargin +1em \bold \size 14
\section Printer Support
}
In all modes, <Print Screen> will print the contents of the screen. In D216 and D410 modes
the DGC Print Window, Print Form, Print Pass Through On, and Print Pass Through Off commands
are also supported. The print pass through commands are generated only by the host. The 
Print Window command can be generated by pressing <Shift><Print Screen>. The Print Form
request can be generated by pressing <Ctrl><Print Screen>.
{\bold \ital mterm} supports print pass thru by creating a temporary file of the data
that was to go to
the printer, and then executing a command against the temporary file. The -pc commandline
option and the printCommand
resource define the command used to print (or copy/move/etc.) the temporary file. To
insert the name of the temporay file in the print command use '\%$1s'. The default value
sends the file to your default printer after making a copy of it. {\bold \ital mterm} 
deletes the
temporary file after the command has been executed. That is why lp commands must use
the -c option. The default print command is 'lp -c \%$1s'.

\node ,Search
{\lmargin +1em \bold \size 14
\section Search
}

\par
{\bold \ital mterm} has a search facility that enables a user to search
the screen and the screen history for characters, words and phrases. Search
forward searches from the top of the visible screen to the end of data. Search
backward searches from the bottom of the screen backwards to the beginning of
data. Searches can be case sensitive or insensitive. When a search has
successfully found a match, the match has a box drawn around it. The box will 
disappear when search is again selected, the marked text scrolls off the 
screen, or the screen is refreshed. The search is done a line at a time, 
from the beginning of the line to the end of the line. If no match is found,
{\bold \ital mterm} will beep. If a match is found, {\bold \ital mterm}
will draw a box around the text that matches the template. The next search
will start 1 character to the right of the first character in the last match.
The box that is drawn only shows up on the screen; it does not affect your
data. The box will be removed when another search is attempted, or the 
currently boxed area is redrawn. 
\par
The search screen can be accessed via the menu system, or by pressing
<ALT><LEFT ARROW>. While in the 'Search for:' field, the <ENTER>
key will cause a search to start in the direction of the last search. 
If no search has taken place, pressing <ENTER> will start the search at
the bottom of the screen and search up the screen and into history.
\par
Each search request starts 1 character to 
the right of the first character in the last match. If the screen has been
scrolled since the last match, the search will start at the bottom of the
screen if you are searching backwards, and at the top of the screen if you
are searching forward.
\par
The following template characters are supported:

\lmargin +8em
\liststart
\item {\bold ?}
Match any single alpha-numeric character (no space). This requires a character
to be present. The search template {\ital map?} would match on {\ital maple,}
drawing a box around {\ital mapl} but not around {\ital map.} The search 
template {\ital map} would find both {\ital map} and {\ital maple,} drawing a 
box around {\ital map.} 

\item {\bold *}
Match zero or more alpha-numeric characters (no spaces). 
The search template {\ital map*} would match on {\ital maple,} drawing a box 
around {\ital maple,} and on {\ital map,} drawing a box around {\ital map.}

\item {\bold #}
Match zero or more characters of any type, including punctuation. This allows 
patterns to span words. It will not span lines. Searching for {\ital ma#pl}
in the text {\ital A man ate an apple} would result in a box being drawn
around {\ital man ate an appl.} Using # as the entire search string has
been special-cased to draw a box around the entire line. This is useful 
for reading tabular information on the screen. The search feature will draw
a box around a line at a time, making text easier to read.


\listend
\lmargin -8em

<ALT><LeftArrow> is the default keyboard accelerator for the search 
window. You can press <ALT><LeftArrow> from the {\bold \ital mterm} window,
and the search window will be displayed. From the search window,
<Enter> will start a search in the direction last used.
The search text, direction, and igonore case
flag will be remembered for the next time you use the search window.
\vsp +4em


# 1804 "mterm.hlp"



\node ,File Select Box
{\lmargin +1em \bold \size 14
\section File Select Box
}
\par
The File Selection item will bring up a file selection box that can
be used for browsing filenames. This can be useful for supplying file
names while in an application. You can browse your filenames and directories
to find the filename you need, and then do a select with the mouse in the 
Selection field. To select the complete pathname you should double click
button one. This will select the entire filename, even if only part of it
is visible in the Selection field. Double clicking on a directory name will
list the files in that directory. The directory name that ends in '..' is
used to represent the parent directory to the current directory.
\par
The Filter field allows you to type in a new template. The Directory window
lists all directories found in the directory displayed on the filter line.
The Files window lists all files that match the template in the directory
display on the filter line.
\par
The OK button types the contents of the Selection field into the mterm
window as if the user typed it. This feature ONLY goes into the mterm
window, not any other window or dialog box. Use cut/paste to copy the
Selection to any input area other than the mterm window (i.e. the filename
field in the Logging dialog box).
\par
The CANCEL button exits the File Selection Box.
\par
The FILTER button will re-list all files matching the supplied filter
template.
\par
The HELP button will bring up this help mesage.
\vsp +4em






\message bad_macro_cmnd
Invalid macro command %s

\message string
%s

\message hanging_up
Hanging up the modem ...

\message bad_label
Label does not exist: %s

\message cant_exec
Can't exec %s

\message cant_get_modem_status
Can't get modem status.

\message waitiing_for_edit
Waiting for edit session to end ...

\message break_sent
A break has been sent ...

\message too_man_paste_requests
Too many paste requests.

\message cursor_frmt
%.256s [row: %d  col: %d]\0

\message Text_bad_message_id
Can't find message string '%s' in helpfile.\0

\message no_resource_file_err
mterm: abnormal exit - there is no resource file (Mterm). 

\message no_memory_err
mterm: abnormal exit - not enough memory.

\message no_such_resource_err
mterm: abnormal exit - resource %s does not exist.

\message bad_option_warn
mterm: Invalid or ambiguous command line option (%s). 
See the mterm man page or online help for a list of valid options.

\message inv_kbd_lang_err
mterm: Invalid KBD_LANG environment variable.

\message no_kbd_lang_warn
mterm: Cannot read keyboard to determine language.
KBD_LANG environment variable not set to a supported country.
Defaulting to US keyboard.

\message cant_read_kbd_lang_err
mterm: abnormal exit - unable to read keyboard language. Use KBD_LANG. 

\message inv_emulation_mode_err
mterm: abnormal exit - the resource emulationMode has an invalid value. 
Valid values are d216, d410, vt100, and vt52.

\message inv_nl_err
mterm: abnormal exit - invalid argument for -nl
Use nl, cr, or crnl.

\message inv_bs_err
mterm: abnormal exit - invalid argument for -bs
Use bs or delete.

\message inv_word_length_err
mterm: abnormal exit - invalid word length specified.
Use 7bit or 8bit.

\message inv_parity_err
mterm: abnormal exit - invalid parity specified.
Use even, odd, or none.

\message inv_flow_control_err
mterm: abnormal exit - invalid flow control specified.
Use none, xon, or cts.

\message inv_baud_rate_warn
mterm: abnormal exit - invalid baud rate.

\message cant_open_file
Could not open %s.

\message cant_delete_file
Could not delete %s

\message cant_open_printfile
Could not open %s.
Can not support print pass through or print screen requests.

\message cant_print_printfile
The print pass through command has completed. However the print
command used to print the temporary print spool file failed. The
temporary print file has not been deleted. The print command line was:
%s

\message print_in_progress
Print in progress...

\message cant_open_font_err
mterm: Could not open Dim Font %s.
Using default font instead.

\message no_fonts_err
mterm: Could not open the requested font or the default fonts.

\message cant_find_charset_err
mterm: abnormal exit - a character set needed by mterm 
was not found in the resource file.

\message cant_find_widget_err
mterm: abnormal exit - can't find widget %s.
You may have an old resource file (Mterm) on your system somewhere 
that needs to be deleted.

\message Main_NoNetwork
The network is not available.\0

\message Main_bad_exit
%s: abnormal exit (exit code=%d)

\message logging_on
Logging on ...\0

\message cant_open_logfile_err
mterm: Could not open log file %s.

\message logfile_in_use_err
mterm: Log file %s already in use.

\message tty_in_use_err
mterm: abnormal exit - %s is already in use.

\message lockfile_exists_err
(%s exists.)

\message cant_create_lockfile_err
mterm: abnormal exit - cannot create %s.

\message set_user_id_bit_msg
mterm: Make sure the mterm executable has the set user id bit set.

\message cant_open_tty_err
mterm: abnormal exit - unable to open %s.

\message inv_resource_file_err
mterm: abnormal exit - invalid resource file (Mterm).

\message version_required_msg
This mterm requires a resource file with a versionText 
string of %s.

\message version_found_msg
The resource file found has a versionText string of
%s.

\message exec_path_msg

      Executable path:  %s

\message exec_version_msg
   Executable version:  %s

\message build_id_msg
             Build id:  %s

\message build_date_msg
           Date built:  %s

\message resource_version_msg
Resource file version:  %s

\message help_version_msg
    Help file version:  %s

\message cant_open_bitmap_warning
Icon bitmap file contains invalid data; using mterm icon instead.

\message bitmap_memory_alloc_warning
Insufficient memory allocation for icon bitmap; using mterm icon instead.

\message inv_bitmap_data_warning
Icon bitmap file contains invalid data; using mterm icon instead.

\message selection_timed_out_warning
A selection has not been made or has timed out.

\message inv_color_set
The color set you requested does not exist.
Defaulting to the default foreground and background colors.

\message inv_color_warning
Invalid color specification. 
Enter a color name or rgb value (#rrbbgg).\0

\message child_died
Received notification that the child process terminated.
\0

# 2095 "mterm.hlp"










\message version
R4.20MU05_5.0\0

\message Main_Unreachable
unreachable\0

\message unknown
unknown\0

\message connected
connected\0

\message password
password:\0

\message username
username:\0

\message invalid
invalid\0

\message logon_string
------\0








\message Child_log_opened

COMMENT: Logging started ...

\message Child_log_closed

COMMENT: Logging stopped ...

\message Child_comment
COMMENT: \0








\message cant_open_pty_err
mterm: abnormal exit - unable to open pty.

\message cant_start_process_err
mterm: abnormal exit - cannot create new process.

\message cant_start_shell_err
mterm: abnormal exit - could not execute '%s'.

\message Ftp_PTY_FAILED
Could not open a PTY to use with ftp.\0

\message Ftp_FORK_FAILED
Could not fork the ftp process necessary for file transfer.\0

\message Ftp_NOT_STARTED
Ftp failed to execute.\0

\message Ftp_NO_BINARY
Could not put ftp into binary mode for file transfer.\0

\message Ftp_READ_TIMEOUT
Read from ftp timed out.

\message Ftp_WRITE_TIMEOUT
Write to ftp timed out.

\message Ftp_WRITE_FAILED
Write to ftp failed.

\message Ftp_READ_FAILED
Read from ftp failed.

\message bad_dup_0
Could not duplicate the slave file descriptor to file 0.\0

\message bad_dup_1
Could not duplicate the slave file descriptor to file 1.\0

\message bad_dup_2
Could not duplicate the slave file descriptor to file 2.\0

\message Kbd_bad_token
mterm: Invalid string token '%s' found in macro.

\message Vid_bad_request
%s: requestor is requesting unsupported selection
target type.

\message Wdg_X_IO_error
X I/O error

\message Wdg_X_error
%s: X error code %s

\message cant_open_slave_pty_err
mterm: abnormal exit - could not open slave pty.

\message icon_num_param_err 
Need exactly one parameter in routine Cb_SetIconAP (see the resource file).

\message icon_inv_param_err 
Invalid parameter in routine Cb_SetIconAP (see the resource file).

\message Color_no_item_selected
You have not selected an item.

\message Color_bad_mtermrc
~/.mtermrc could not be opened.

\message get_rid_of_comments






% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Help System "Help on Help"
% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\node About Help
\level 1
\section The Help System,no-text,hide-toc-children
\level 2
\section About Help,no-text,hide-toc-children

The help system provides a way for you to view information, including
application information, links between related ideas, a history
facility, a table of contents, and resource specification capabilities.

You can click on any of the following topics for more information:

{\lmargin 0.30in
\parindent 0in
{\fontspec symbol } \link {Using Help,Using Help}

{\fontspec symbol } \link {Customizing Help,Customizing Help}}

A {\ital help document} contains information about an
application (such as Mterm or Mxdb) and is organized into sections,
like a book.  As within a book, sections in a help document may be
divided into more sections, which may be divided into more sections
yet. The table of contents lists the help document's contents by
sections.

The information contained in a help document is divided into
{\ital nodes}.  Nodes correspond to the pages of a book.
These "pages" of information are displayed in the help display area.

There is often a connection from a phrase in one section of a help
document to related text in another section. These connections are
known as {\ital links}. Underlined text in the help
display window indicates a link to related text elsewhere in the help
document.

\node
\level 2
\section Using Help,no-text,hide-toc-children

This section describes the user interface components of the help system.
The main window appears when your application program calls the help
system.  The window consists of four main areas: the menu bar, the node
title area, the help display area, and the control panel.  These areas are
illustrated in the diagram below.  For more information about any area
click on it's underlined label.

\break
\break
{\lmargin 0.80in
\box 6in,7in,0.03in
\lmargin +0.1in
\vsp +0.1in
\box 5.82in,0.4in,0.03in
\size 14
\vsp -0.16in
\bold \lmpos 21em \link{Menu Bar,The Menu Bar}
\break
\box 5.82in,0.4in,0.03in
\vsp -0.16in
\lmpos 21.2em \link{Title Area,Node Title Area}
\break
\box 5.82in,5.4in,0.03in
\vsp +2.2in
\lmpos 17.2em \link{Help Display Area,Help Display Area}
\break
\vsp +2.65in
\box 5.82in,0.4in,0.03in
\vsp -0.16in
\lmpos 19em \link{Control Panel,The Control Panel}
}

\node
\level +
\section The Menu Bar,no-text,hide-toc-children

The menu bar, located at the top of the window, contains the View
and Help menus. To use a menu, move your cursor to the menu name and
press the mouse's left button. The menu will appear and show you what
commands you can choose from. To select a menu item, move your cursor
to the item and release the left button. If you don't wish to choose
an item from that menu, release the left button anywhere outside of
the menu.

You can browse through the menus in the menu bar by moving the cursor
across the menu title.

\node
\level +
\section The View Menu,no-text,hide-toc-children

The View menu contains two entries: Table of Contents and History.

\liststart

\item {\bold Table of Contents}
Choosing the Table of Contents entry displays, in a dialog box, the section
entries in the help document.  To display a section in the help display
area, move your cursor to the section entry listed in the dialog box and
double-click the left button of your mouse. Or, click the left button once
and click on the OK box with the left button.

If there are more section entries than can appear in the dialog box,
horizontal and vertical scrollbars appear.  Use scrollbars to move
text in the dialog box so that you can see the rest of the section
entries.

The help system can expand or contract the table of contents. If a
section entry in the dialog box is followed by an ellipsis, clicking
the mouse's right button on that section entry will display any hidden
subsections. Clicking the right button on an entry with subsections
beneath it will cause that portion of the table of contents to contract
and an ellipsis will appear after the section entry.  You can skim
through the contracted table of contents and then expand sections
to quickly find the information you want.

\item {\bold History} 
Choosing the History entry displays, in a dialog box, the nodes that you
have visited while using the help system.  After you visit a node, its name
is added to the bottom of the history list (it can be added to the top of
the list instead if you specify a value of True for the history.insertAtTop
resource; see the section \link{Customizing Help,Customizing Help}).

You can display a node from the history list in the help display area
by moving your cursor to the node listed in the dialog box and
double-clicking the left button of your mouse. Alternatively, click
the left button once and click on the OK box with the left button.

If there are more nodes than can appear in the dialog box, horizontal
and vertical scrollbars appear.  Use scrollbars to move text in the
dialog box so that you can see the rest of the nodes.
\listend

\node
\section The Help Menu,no-text,hide-toc-children

The Help menu contains three entries: About Help, Using Help, and
Customizing Help.

\liststart

\item {\bold About Help} 
Choosing the About Help entry displays general information about the help
system.

\item {\bold Using Help}
Choosing the Using Help entry displays information that describes how to
use the help system.

\item {\bold Customizing Help}
Choosing the Customizing Help entry display information that describes how
to change the appearance and behavior of the help system through X resource.
\listend

\node
\level -
\section Node Title Area,no-text,hide-toc-children

The node title area displays the name of the current node (as it is
displayed in the table of contents and history) and is located below
the menu bar and above the help display area.

\node
\section Help Display Area,no-text,hide-toc-children

This area of the window displays the help document, which contains
information about an application. Underlined text in the help display
window indicates a link to related text elsewhere in the help document.
To view the related information, click your mouse's left
button on the underlined text.  The new information will be displayed
in the help display area.

If the underlined phrase has more than one link associated with it,
the Node Selection dialog box will appear. This dialog box lists the
node names from which you can choose. To choose a node, move your
cursor to the node name listed in the dialog box and double-click
the left button of your mouse. Alternatively, click the left button
once and click on the OK box with the left button.

Only one Node Selection dialog box will appear for each help session.
If node selection is necessary and the dialog box already exists,
the help system replaces the node name list with a new list.   

The Node Selection dialog box will remain on the screen until you
close it, either explicitly with the Close button or implicitly by
closing the help system or exiting from the application program. You
might want to move the dialog box out of the help display area; with
most window managers, move your cursor to the title bar of the Node
Selection box, press and hold the left button, move the cursor to
the position where you want the dialog box, and release the button.

If the node displayed in the help display area contains more information
than can appear in the area, horizontal and vertical scrollbars appear. 
Use scrollbars to move text in the help display area so that you can
see the rest of the information.

Note that horizontally resizing the main window will not affect word
wrap margins, which are specified in the help source file. Vertically
resizing the main window will allow more information to appear in
the help display area.

\node
\section The Control Panel,no-text,hide-toc-children

The Control Panel contains four buttons: Next, Previous, Undo, and
Close.

\liststart
\item {\bold Next}
When you click the Next button, the help system displays the next
node of the help document. If there is no node after the current node,
this button's text is shaded with gray to show that the button is
inoperative.

\item {\bold Previous}
When you click the Previous button, the help system displays the previous
node of the help document. If there is no node before the current
node, this button's text is shaded with gray to show that the button
is inoperative.

\item {\bold Undo}
The help system removes the previously viewed node from the top of
the history list and displays it when you click the Undo button. If
the history list is empty, this button is shaded with gray to show
that it is inoperative.

\item {\bold Close}
To remove the help window and any help dialogs from the screen, click
the Close button. The Close button does not cause you to exit from
the application that called the help system. The help window and any
dialogs will reappear when the application calls the help system again.

\listend

\node
\section Node Selection Dialogs,no-text,hide-toc-children

{\bold Table of Contents and History Dialog Boxes:} Both
the Table of Contents and History dialog boxes will remain on the
screen until you close them, either explicitly with the Close button
or implicitly by closing the help system or exiting from the
application program.  You might want to move a dialog box out of the
help display area; with most window managers, move your cursor to the
title bar of the Table of Contents or History box, press and hold the
left button, move the cursor to the position where you want the dialog
box, and release the button.

\node
\level -
\section Customizing Help,no-text,hide-toc-children
Xhelp can be customized using command-line options and resources;  
many Xhelp features can be customized by both command-line options and  
X resources. Resources are generally useful to define several features
commonly used or used as a group. Command-line options are more useful 
for exceptions to these common features. For more information about 
resources and resource files see the man page for Xdefaults and X.

Use the following syntax for the specification of help system resources:

{
\lmargin 0.0385pw
{\ital application_name_or_class}{\bold .help.}{\ital resource_specification}

\lmargin 0.0385pw
{\ital application_name_or_class}{\bold .help*}{\ital resource_specification}
}

Placing a period between components (like {\ital
application_name_or_class}{\bold .help}\ and {\bold help.}{\ital resource_specification}) means
that the left component must be the parent of the right component.
Since each application is the parent of its help system, you would
begin an Mterm help system resource specification with "Mterm.help" and
follow that with the rest of the specification.

Placing an asterisk, which is a wildcard character, between components
(such as {\bold help*}{\ital
resource_specification}) means that the left component must be an
ancestor of the right component. This is helpful when you want to
specify a resource not just for one item, but for that item and all
the items that it contains. To specify a resource (in this example,
the foreground color) for all of an application's descendants, use
this syntax:

{
\lmargin 0.0385pw
{\ital application_name_or_class}{\bold *}{\ital foreground_specification}.
}

The {\ital resource_specification}\ variable consists of
a resource name followed by a colon, one or more spaces, and a value.
Here are some examples:

{\lmargin 0.0385pw \fontspec example
Mterm.help*foreground: dark slate gray\break
Mterm.help*background: light blue\break
Mterm.help.history.insertAtTop: True}

The first example above specifies that the foreground color
of Mterm's help system, including all of its descendants, will be dark
slate gray. The second example specifies that the background color
for Mterm's help system will be light blue. The last example specifies
that new history items in Mterm's help system will be added to the
top of the history list.

Explicitly stated resource specifications take precedence over general
resource specifications, as shown in the following list:

{\lmargin 0.0385pw \fontspec example
Application.help.item.resource  \lmpos 35em (highest precedence)\break
Application.help.item*resource\break
Application.help*resource\break
Application*resource \lmpos 35em (lowest precedence)}


If neither you nor an application's help system does not specify a
particular resource for the help system, the value for that resource
is, by default, the application's value for that resource. For instance,
if you do not specify a foreground color for Mterm's help system, but
did specify black for Mterm's foreground color, the Mterm help system's
foreground color will be black.

Some common resources are described below, in alphabetical order.

\node
\level +
\section Specifying the Background Color,no-text,hide-toc-children

The background color determines the color of everything except text.
The default is white for monochrome displays and blue for color displays.
This example specifies that the background color for Mterm's help system
will be light blue:

{\lmargin 0.0385pw \fontspec example
Mterm.help*background: light blue}

To make the background color for all help windows light blue, use
this specification:

{\lmargin 0.0385pw \fontspec example
*help*background: light blue}

See the {\bold rgb.txt}\ file, usually located in {\bold /usr/lib/X11},
for the list of colors to choose from.

\node 
\section Specifying Fonts,no-text,hide-toc-children

The fontList resource specifies the font for text in the help system
window; if you do not specify a font, the window will contain text
in the default font, which is the first font in the application's
fontList.

You can use any valid font description as the value for this resource;
use the {\bold xlsfonts}\ command to list the valid
fonts. Note that the font size will affect the size of the window
frame and its menus.

This example specifies that the font for the Mterm help system's
interface (including menus, labels, and button names) will be 9x15;
use the asterisk to denote that this font applies for the help system
window and all of its subwindows:

{\lmargin 0.0385pw \fontspec example
Mterm.help*fontList: 9x15}

The next example specifies some fonts for the help system's help text,
located in the ViewWindow area (the ViewWindow area is the area of
each window in which you view text). The ViewWindow area supports
named fonts for various classes of text. Except for "default,"
classes are application defined.

{\lmargin 0.0385pw \fontspec example
Mterm.help.viewWindow.fontList: \\\break
\lmpos 5em  *courier*medium-r*12*=default, \\\break
\lmpos 5em *courier*medium-r*12*=normal, \\\break
\lmpos 5em *courier*medium-o*12*=italic, \\\break
\lmpos 5em *courier*bold-r*12*=bold
}

The font named "default" will be used when the system cannot find
a referenced font.

\node
\section Specifying the Foreground Color,no-text,hide-toc-children

The foreground color is the color in which the text in the help system's
window and menus is displayed. For example, the foreground color determines
the color of the menu name "View" and the color of the options
listed in that menu. The default is black for both monochrome and 
color displays. This example specifies that the foreground color of
Mterm's help system will be dark slate gray:

{\lmargin 0.0385pw \fontspec example
Mterm.help*foreground: dark slate gray}

To make the foreground color for all help windows dark slate gray,
use this specification:

{\lmargin 0.0385pw \fontspec example
*help*foreground: dark slate gray}

See the {\bold rgb.txt}\ file, usually located in
{\bold /usr/lib/X11}, for the list of colors to choose
from.

\node
\section Specifying Window Size and Placement,no-text,hide-toc-children

The geometry resource specifies the size and placement of the help
system window. The value of {\ital geometry}\ is

{\lmargin 0.0385pw \fontspec example
[{\ital width}{\bold x}{\ital height}][{\bold +}{\ital xoff}{\bold +}{\ital yoff}]
}

The {\ital width}\ and {\ital height}\
values are the dimensions of the help system window. The\  {\ital xoff}\ (x-offset) and {\ital yoff}\ (y-offset)
values determine the window's location. All of the values are in
pixels.

A positive x-offset specifies the distance that the left
edge of the window is offset from the left side of the display, while
a negative x-offset specifies the distance the right edge of the
window is offset from the right side of the display. A positive y-offset
specifies the distance that the top edge of the window is offset from
the top of the display, while a negative y-offset specifies the
distance that the bottom edge of the window is offset from the bottom
of the display.

If you specify the window size but not the location, you must move
the window to its location . If you specify the location but not the
window size, the help system window uses the default size of 602 pixels
by 811 pixels.

The following example will place a 800 pixel by 800 pixel help system
window in the upper left corner (10 pixels from both the left and
top edges) of the display when the application program (Mterm in this
case) calls the help system:

{\lmargin 0.0385pw \fontspec example
Mterm.help.geometry: 800x800+10+10}

\node
\section Specifying History Item Insertion,no-text,hide-toc-children

The history.insertAtTop resource specifies where new history items
will be inserted. If this resource's value is True, new history items
are added to the top of the history list. If the value is False, items
are inserted at the bottom. This example would cause new history items
in Mterm's help system will be added to the top of the history list:

{\lmargin 0.0385pw \fontspec example}
Mterm.help.history.insertAtTop: True}

\node ,,_none
\section Specifying Scrollbar Placement,no-text,hide-toc-children

The scrollbarPlacement resource specifies where the help system's
scrollbars will be placed in the help system window.  The value of
{\ital scrollbarPlacement}\ is

{\lmargin 0.0385pw \fontspec example
{\ital verticalplacement}{\bold _}{\ital horizontalplacement}}

The value of {\ital verticalplacement}\ can be TOP or
BOTTOM. The value of {\ital horizontalplacement}\ can be
LEFT or RIGHT.

This example will place scrollbars at the top and right side of Mterm's
help system window:

{\lmargin 0.0385pw \fontspec example
Mterm.help*scrollbarPlacement: TOP_RIGHT}

% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Help System Error Messages
% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\message Fatal Error
Fatal Error
\message Error
Error
\message Warning
Warning
\message Debugging
Debug
\message Parse Error
Parse Error
\message UI Error
UI Error
\message Default Error
Default Error
\message parse_begin_wo_end
Node %s: No end group (}) found for begin group ({) on line %d
\message parse_end_before_begin
Node %s: Extra end group (}) found on line %d
\message parse_unexpected_eol
Node %s: Unexpected text on line %d before end of line
\message parse_invalid_unit
Node %s: Invalid unit encountered on line %d
\message parse_invalid_style
Node %s: Invalid style encountered on line %d
\message parse_no_left_brace
Node %s: Link token encountered on line %d with no begin group
\message parse_no_right_brace
Node %s: Link token encountered on line %d with no end group
\message parse_unexpected_end_of_node
Node %s: Unexpected end of node encountered on line %d
\message parse_unexpected_end_of_draw
Node %s: Unexpected end of drawing command encountered on line %d
\message parse_invalid_token
Node %s: Invalid token %s encountered on line %d
\message parse_invalid_command_placement
Node %s: Invalid command placement on line %d
\message parse_display_before_end_display
Node %s: Display before end display encountered on line %d
\message parse_end_display_before_display
Node %s: End display encountered before display on line %d
\message parse_display_wo_end_display
Node %s: Display without end display encountered on line %d
\message parse_number_out_of_range
Node %s: Number out of range on line %d
\message parse_bad_node_token
Node %s: Invalid node command encountered on line %d
\message parse_no_node_name
Node %s: No node or section name found
\message parse_begin_end_consistency
Node %s: Grouping level after item must be the same as before on line %d
\message parse_invalid_argument
Invalid argument encountered on line %d
\message parse_invalid_section_command
Invalid section command encountered on line %d
\message parse_bad_node_command
Invalid node command format on line %d
\message parse_bad_draw_command
Invalid draw command format on line %d
\message parse_too_many_levels
Too many list levels on line %d
\message ui_load_font_bad_name
Font %s not found
\message ui_unable_to_create_gc
Unable to create graphics context
\message default_get_node_error
Unable to get node %s
\message last_message_to_avoid_evil_bug
bogus


