<\body> As explained before, the configuration file /progs/init-.scm> of a plug-in with name > should contain an instruction of the type <\scheme-fragment> (plugin-configure \ \ ) Here follows a list of the available >: <\description-dash> )>>>This option specifies a sanity > which needs to be satisfied by the plug-in. Usually, it is checked that certain binaries or libraries are present on your system. If the condition fails, then will continue as whether your plug-in did not exist. In that case, further configuration is aborted. The option usually occurs first in the list of configuration options. )>>>This option specifies a expression > which evaluates to the version of the plug-in. )>>>This command is only executed when the version of the plug-in changed from one execution of to another one. This occurs mainly when installing new versions of or helper applications. )>>>This option executes the expression >. It usually occurs just after the option, so that the plug-in will only be configured if the plug-in really exists. For large plug-ins, it is important to keep the file /progs/init-.scm> small, because it will be rerun each time you start . In order to reduce the boot time, most commands of the plug-in therefore occur in separate modules, some of which may be loaded by the initialization command. )>>>This option specifies that the plug-in is able to evaluate expressions over a pipe, using a helper application which is launched using the shell-command >. )>>>This option is similar to , except that the extern application is now linked dynamically. For more information, see the section about . )>>>This option indicates that the plug-in supports an evaluator for interactive shell sessions. An item > will be inserted to the menu in order to launch such sessions. )>>>If the plug-in can be used as an evaluator, then this option specifies the function > which is used in order to transform trees to strings. )>>>This command is similar to the option except that it is used to transform special commands to strings. >>This command indicates that the plug-in supports tab-completion. >>This command indicates that the plug-in provides a routine for testing whether the input is complete. <\initial> <\collection>