minicom.1

在MAC OS下的一个可以直接调试modem的工具minicom,类似于是在windows下的超级终端.

.B R - Modem has DCD line
If your modem, and your O/S both support the DCD line (that goes 'high'
when a connection is made) minicom will use it. When you have this option
on, minicom will also NOT start dialing while you are already online.
.TP 0.5i
.B S - Status line shows DTE speed / line speed
You can toggle the status line to show either the DTE speed (the speed 
which minicom uses to communicate with your modem) or the line speed
(the speed that your modem uses on the line to communicate with the 
other modem). Notice that the line speed may change during the connection,
but you will still only see the initial speed that the modems started
the connection with. This is because the modem doesn't tell the program
if the speed is changed. Also, to see the line speed, you need to have
the modem set to show it in the connect string. 
Otherwise you will only see 0 as the line speed.
.TP 0.5i
.B T - Multi-line untag
You can toggle the feature to untag entries from the dialing directory when
a connection is established to a multi-line BBS. All the tagged entries that
have the same name are untagged.
.PD 1
.PP
.RE
.RS 0.5i
.B Note that a special exception is made for this menu: every user
.B can change all parameters here, but some of them will not be saved.
.RE
.PP
.B "Screen and keyboard"
.RS 0.25i
.PD 0
.TP 0.5i
.B A - Command key is
the 'Hot Key' that brings you into command mode. If this is set
to 'ALT' or 'meta key', you can directly call commands
by alt-key instead of HotKey-key.
.TP 0.5i
.B B - Backspace key sends
There still are some systems that want a VT100 to send DEL instead of
BS. With this option you can enable that stupidity.  (Eh, it's even on
by default...)
.TP 0.5i
.B C - Status line is
Enabled or disabled. Some slow terminals (for example, X-terminals)
cause the status line to jump "up and down" when scrolling, so you can
turn it off if desired. It will still be shown in command-mode.
.TP 0.5i
.B D - Alarm sound
If turned on, minicom will sound an alarm (on the console only) after
a successful connection and when up/downloading is complete.
.TP 0.5i
.B E - Foreground Color (menu)
indicates 
the foreground color to use for all the configuration windows in minicom.
.TP 0.5i
.B F - Background Color (menu)
indicates the background color to use for 
all the configuration windows in minicom. Note that minicom will not allow 
you to set foreground and background colors to the same value.
.TP 0.5i
.B G - Foreground Color (term)
indicates the foreground color to use in the terminal window.
.TP 0.5i
.B H - Background Color (term)
indicates the background color to use in 
the terminal window. Note that minicom will not allow you to set foreground 
and background colors to the same value.
.TP 0.5i
.B I - Foreground Color (stat)
indicates the foreground color to use in for the status bar.
.TP 0.5i
.B J - Background Color (stat)
indicates the color to use in for the
status bar. Note that minicom will allow you to set the status bar's
foreground and background colors to the same value. This will effectively
make the status bar invisible but if these are your intentions, please
see the option
.TP 0.5i
.B K - History buffer size
The number of lines to keep in the history buffer (for backscrolling).
.TP 0.5i
.B L - Macros file
is the full path to the file that holds
macros. Macros allow you to define a string to be sent when you press
a certain key. In minicom, you may define F1 through F10 to send
up to 256 characters [this is set at compile time]. The filename you
specify is verified as soon as you hit ENTER. If you do not have permissions
to create the specified file, an error message will so indicate and you
will be forced to re-edit the filename. If you are permitted to create
the file, minicom checks to see if it already exists. If so, it assumes
it's a macro file and reads it in. If it isn't, well, it's your problem :-)
If the file does not exist, the filename is accepted.
.TP 0.5i
.B M - Edit Macros
opens up a new window 
which allows you to edit the F1 through F10 macros. 
.TP 0.5i
.B N - Macros enabled
- Yes or No. If macros are disabled, the F1-F10
keys will just send the VT100/VT220 function key escape sequences.
.TP 0.5i
.B O - Character conversion
The active conversion table filename is shown here. If you can see no
name, no conversion is active. Pressing O, you will see the conversion 
table edit menu.
.RS 0.5i
.PD 1
.TP 0.25i
.B "Edit Macros"
Here, the macros for F1 through F10 are defined. The bottom of the
window shows a legend of character combinations that have special meaning.
They allow you to enter special control characters with plain text by
prefixing them with a '^', in which '^^' means '^' itself. You can
send a 1 second delay with the '^~' code. This is useful when you are
trying to login after ftp'ing or telnet'ing somewhere. 
You can also include your current username and password from the phone 
directory in the macros with '\\u' and '\\p', respectively. If you need
the backslash character in the macro, write it doubled as '\\\\'.
To edit a macro, press the number (or letter for F10) and you will be 
moved to the end of the macro. When editing the line, you may use the 
left & right arrows, Home & End keys, Delete & BackSpace, and ESC and 
RETURN.  ESC cancels any changes made while ENTER accepts the changes.
.PD 1
.TP 0.25i
.B "Character conversion"
Here you can edit the character conversion table. If you are not an
American, you know that in many languages there are characters that are
not included in the ASCII character set, and in the old times they may
have replaced some less important characters in ASCII and now they are
often represented with character codes above 127. AND there are various
different ways to represent them. This is where you may edit conversion
tables for systems that use a character set different from the one on your
computer.
.TP 0.5i
.B A - Load table
You probably guessed it. This command loads a table from the disk.
You are asked a file name for the table.
Predefined tables .mciso, .mcpc8 and .mcsf7 should be included with the
program. Table .mciso does no conversion, .mcpc8 is to be used for 
connections with systems that use the 8-bit pc character set, and .mcsf7
is for compatibility with the systems that uses the good old 7-bit coding
to replace the characters {|}[]\\ with the diacritical characters used in
Finnish and Swedish.
.TP 0.5i
.B B - Save table
This one saves the active table on the filename you specify.
.TP 0.5i
.B C - edit char
This is where you can make your own modifications to the existing table.
First you are asked the character value (in decimal) whose conversion you
want to change. Next you'll say which character you want to see on your 
screen when that character comes from the outside world. And then you'll
be asked what you want to be sent out when you enter that character from
your keyboard.
.TP 0.5i
.B D - next screen
.TP 0.5i
.B E - prev screen
Yeah, you probably noticed that this screen shows you what kind of
conversions are active. The screen just is (usually) too small to show
the whole table at once in an easy-to-understand format. This is how you can
scroll the table left and right.
.TP 0.5i
.B F - convert capture
Toggles whether or not the character conversion table is used when
writing the capture file.
.RE
.RE
.PD 1
.TP 0.25i
.B "Save setup as dfl"
Save the parameters as the default for the next time the program is
started. Instead of dfl, any other parameter name may appear, depending
on which one was used when the program was started.
.TP 0.25i
.B "Save setup as.."
Save the parameters under a special name. Whenever Minicom is started
with this name as an argument, it will use these parameters. This
option is of course privileged to root.
.TP 0.25i
.B "Exit"
Escape from this menu without saving.  This can also be done with ESC.
.TP 0.25i
.B "Exit from minicom"
Only root will see this menu entry, if he/she started minicom with the '\-s'
option. This way, it is possible to change the configuration without
actually running minicom.
.PD 1
.SH "STATUS LINE"
The status line has several indicators, that speak for themselves.
The mysterious APP or NOR indicator probably needs explanation. The
VT100 cursor keys can be in two modes: applications mode and cursor
mode. This is controlled by an escape sequence. If you find that
the cursor keys do not work in, say, vi when you're logged in using
minicom then you can see with this indicator whether the cursor keys
are in applications or cursor mode. You can toggle the two with the
C-A I key. If the cursor keys then work, it's probably an error in
the remote system's termcap initialization strings (is).
.PD 1
.SH "LOCALES"
Minicom has support for local languages. This means you can change most
of the English messages and other strings to another language by setting
the environment variable LANG.
.PD 1
.SH MISC
If minicom is hung, kill it with SIGTERM . (This means kill \-15, or
since sigterm is default, just plain "kill <minicompid>". This will
cause a graceful exit of minicom, doing resets and everything.
You may kill minicom from a script with the command "! killall \-9 minicom"
without hanging up the line. Without the \-9 parameter, minicom first 
hangs up before exiting.
.PP
Since a lot of escape sequences begin with ESC (Arrow up is ESC [ A),
Minicom does not know if the escape character it gets is you pressing
the escape key, or part of a sequence.
.PP
An old version of Minicom, V1.2, solved this in a rather crude way:
to get the escape key, you had to press it 
.IR twice .
.PP
As of release 1.3 this has bettered a little: now a 1-second timeout
is builtin, like in vi. For systems that have the select() system call
the timeout is 0.5 seconds. And... surprise: a special Linux-dependant
.BR hack " :-) was added. Now, minicom can separate the escape key and"
escape-sequences. To see how dirty this was done, look into wkeys.c.
But it works like a charm!
.SH FILES
Minicom keeps it's configuration files in one directory, usually
/var/lib/minicom, /usr/local/etc or /etc. To find out what default
directory minicom has compiled in, issue the command \fIminicom -h\fP.
You'll probably also find the demo files for \fBrunscript\fP(1),
and the examples of character conversion tables either there or 
in the subdirectories of /usr/doc/minicom*. The conversion tables are
named something like mc.* in that directory, but you probably want to
copy the ones you need in your home directory as something beginning
with a dot.
.sp 1
.nf
minicom.users
minirc.*
$HOME/.minirc.*
$HOME/.dialdir
$HOME/minicom.log
/usr/share/locale/*/LC_MESSAGES/minicom.mo
.fi
.SH SEE ALSO
.BR runscript (1)
.SH BUGS
Please report any bugs to
.IR [e-mail] .
Thank you!
.SH AUTHORS
The original author of minicom is Miquel van Smoorenburg ([e-mail]).
He wrote versions up to 1.75.
.br
Jukka Lahtinen ([e-mail], [e-mail]) has been responsible
for new versions since 1.78, helped by some other people, including:
.br
[e-mail] wrote the History buffer searching to 1.79.
.br
Arnaldo Carvalho de Melo ([e-mail]) did the internationalization 
and the Brasilian Portuguese translations.
.br
Jim Seymour ([e-mail]) wrote the multiple modem support 
and the filename selection window used since 1.80.
.br
Tomohiro Kubota ([e-mail]) wrote the Japanese translations 
and the citation facility, and did some fixes.
.br
Gael Queri ([e-mail]) wrote the French translations.
.br
Arkadiusz Miskiewicz ([e-mail]) wrote the Polish translations.
.br
Kim Soyoung ([e-mail]) wrote the Korean translations.
.br
Jork Loeser ([e-mail]) provided the socket extension.
.PP
Most of this man page is copied, with corrections, from the original minicom
README, but some pieces and the corrections are by Michael K. Johnson.
.PP
Jukka Lahtinen ([e-mail]) has added some information of the changes 
made after version 1.75.