|Purpose:||Load, unload, or display information about plugins|
|Format:||PLUGIN [/B /C /F /I /K /L /P[n] /U /V] plugin ...|
Plugins allow you to write your own internal variables, variable functions, and internal commands, put them in a DLL, and have TCC load them at startup. Plugin names will override existing internal names, so you can extend and/or replace internal variables and commands. When TCC starts, it will automatically load any plugins in the default directory (the subdirectory PLUGINS\ in the TCC installation directory). The plugins will be loaded before the startup file (TCSTART) are executed.
You can also write keystroke plugins that will be called for every keystroke entered at the command line. A keystroke plugin can perform actions when a specific key is entered, or even change the key before passing it back to the command processor.
If no options are specified, PLUGIN will display the currently loaded plugins and their internal variables, variable functions, and commands.
You can specify a particular plugin to execute by prefixing the function / variable / command name with the plugin name and a $. For example:
See the Plugin SDK for more information on developing plugins.
|/I||Display information about the specified plugin, including the name, author, author's email and web addresses, description, function list, version and build numbers. The /I option supports wildcards.|
|/L||Loads the specified plugins. If the filename is *, load all plugins from the default directory (the subdirectory PLUGINS\ in the TCC installation directory).|
|/P[n]||Wait for a key to be pressed after each screen page before continuing the display. Your options at the prompt are explained in detail under Page and File Prompts. The /P option has an optional argument n that specifies the number of seconds to wait for a keystroke before continuing.|