Sophie: garlic-1.6-6 i586

garlic-1.6-6.i586.rpm

<html>

<head>
<title>
EXE, EXECUTE
</title>
</head>

<h1 align=center>

EXE, EXECUTE

</h1>

<hr size="3">

<font color=#880000>
<b>
NAME
<br>
</b>
</font>


EXE, EXECUTE - load and execute garlic script.
<br><br>


<font color=#880000>
<b>
SYNOPSIS
<br>
</b>
</font>


EXE file_name
<br>
EXECUTE file_name
<br><br>


<font color=#880000>
<b>
DESCRIPTION
<br>
</b>
</font>


Load and execute the specified garlic script. The garlic script file should
contain garlic commands. There is only one command which is not executed
if added into garlic script: the EXE command. This is done to avoid endless
loops; the script which executes itself will generate an endless loop. If you
don't like it, change to source file execute_command1.c
(use the source, Luke!). Examples:
<br><br>


<table border=2 cellspacing=2 cellpading=0>

<td align="left">

COMMAND

</td>

<td align="left">

DESCRIPTION

</td>

<tr>

<td align="left">

exe dance.script

</td>

<td align="left">

Execute the script which loads trp.pdb
<br>
and forces this molecule to play something
<br>
similar to Argentinian tango.

</td>

</table>

<br>

<font color=#880000>
<b>
RELATED COMMANDS
<br>
</b>
</font>


LOG may be used to store commands used during a garlic session. The log file
may be used later as a script.
<br><br>


<hr size="3">

</html>