1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
<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>
|
