> <\body> As explained before, the configuration file /progs/init-.scm> of a plug-in with name > should contain an instruction of the type <\scm-code> (plugin-configure \ \ ) Here follows a list of the available >: <\description-dash> )>>>Specify where to search for the plug-in under windows. The > is the usual place where the plug-in is installed. The > is the place where to look for the binary executable corresponding to the plug-in, relative to the >. )>>>Analogous to , but under . )>>>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 a list of available versions 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 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. It should be noticed that the configuration of the plug-in > automatically creates a few predicates: <\description> ?>>>Test whether the plug-in is fully operational (all requirements are met). ?>>>Test whether > is the current programming language. -scripts?>>>Test whether > is the current scripting language. >