Un outil pour savoir si une commande est posix - retour accueil
git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |
fc.html (22540B)
1 <!-- Copyright 2001-2024 IEEE and The Open Group, All Rights Reserved -->
2 <!DOCTYPE HTML>
3 <html lang="en">
4 <head>
5 <meta name="generator" content="HTML Tidy for HTML5 for Linux version 5.8.0">
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group rhtm tool v1.2.4 -->
8 <!-- Copyright (c) 2001-2024 The Open Group, All Rights Reserved -->
9 <title>fc</title>
10 </head>
11 <body bgcolor="white">
12 <div class="NAVHEADER">
13 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
14 <tr class="nav">
15 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/false.html" accesskey="P"><<<
16 Previous</a></td>
17 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
18 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/fg.html" accesskey="N">Next >>></a></td>
19 </tr>
20 </table>
21 <hr align="left" width="100%"></div>
22 <script language="JavaScript" src="../jscript/codes.js"></script><basefont size="3">
23 <center><font size="2">The Open Group Base Specifications Issue 8<br>
24 IEEE Std 1003.1-2024<br>
25 Copyright © 2001-2024 The IEEE and The Open Group</font></center>
26 <hr size="2" noshade>
27 <a name="top" id="top"></a> <a name="fc" id="fc"></a> <a name="tag_20_44" id="tag_20_44"></a><!-- fc -->
28 <h4 class="mansect"><a name="tag_20_44_01" id="tag_20_44_01"></a>NAME</h4>
29 <blockquote>fc — process the command history list</blockquote>
30 <h4 class="mansect"><a name="tag_20_44_02" id="tag_20_44_02"></a>SYNOPSIS</h4>
31 <blockquote class="synopsis">
32 <div class="box"><code><tt><sup>[<a href="javascript:open_code('UP')">UP</a>]</sup> <img src="../images/opt-start.gif" alt=
33 "[Option Start]" border="0"> fc</tt> <b>[</b><tt>-r</tt><b>] [</b><tt>-e</tt> <i>editor</i><b>] [</b><i>first</i>
34 <b>[</b><i>last</i><b>]]</b> <tt><br>
35 <br>
36 fc -l</tt> <b>[</b><tt>-nr</tt><b>] [</b><i>first</i> <b>[</b><i>last</i><b>]]</b> <tt><br>
37 <br>
38 fc -s</tt> <b>[</b><i>old</i><tt>=</tt><i>new</i><b>] [</b><i>first</i><b>]</b> <tt><img src="../images/opt-end.gif" alt=
39 "[Option End]" border="0"></tt></code></div>
40 <tt><br></tt></blockquote>
41 <h4 class="mansect"><a name="tag_20_44_03" id="tag_20_44_03"></a>DESCRIPTION</h4>
42 <blockquote>
43 <p>The <i>fc</i> utility shall list, or shall edit and re-execute, commands previously entered to an interactive <a href=
44 "../utilities/sh.html"><i>sh</i></a>.</p>
45 <p>The command history list shall reference commands by number. The first number in the list is selected arbitrarily. The
46 relationship of a number to its command shall not change except when the user logs in and no other process is accessing the list,
47 at which time the system may reset the numbering to start the oldest retained command at another number (usually 1). When the
48 number reaches an implementation-defined upper limit, which shall be no smaller than the value in <i>HISTSIZE</i> or 32767
49 (whichever is greater), the shell may wrap the numbers, starting the next command with a lower number (usually 1). However, despite
50 this optional wrapping of numbers, <i>fc</i> shall maintain the time-ordering sequence of the commands. For example, if four
51 commands in sequence are given the numbers 32766, 32767, 1 (wrapped), and 2 as they are executed, command 32767 is considered the
52 command previous to 1, even though its number is higher.</p>
53 <p>When commands are edited (when the <b>-l</b> option is not specified), the resulting lines shall be entered at the end of the
54 history list and then re-executed by <a href="../utilities/sh.html"><i>sh</i></a>. The <i>fc</i> command that caused the editing
55 shall not be entered into the history list. If the editor returns a non-zero exit status, this shall suppress the entry into the
56 history list and the command re-execution. Any command line variable assignments or redirection operators used with <i>fc</i> shall
57 affect both the <i>fc</i> command itself as well as the command that results; for example:</p>
58 <pre>
59 <tt>fc -s -- -1 2>/dev/null
60 </tt></pre>
61 <p>reinvokes the previous command, suppressing standard error for both <i>fc</i> and the previous command.</p>
62 </blockquote>
63 <h4 class="mansect"><a name="tag_20_44_04" id="tag_20_44_04"></a>OPTIONS</h4>
64 <blockquote>
65 <p>The <i>fc</i> utility shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax
66 Guidelines</i></a> .</p>
67 <p>The following options shall be supported:</p>
68 <dl compact>
69 <dd></dd>
70 <dt><b>-e </b><i>editor</i></dt>
71 <dd>Use the editor named by <i>editor</i> to edit the commands. The <i>editor</i> string is a utility name, subject to search via
72 the <i>PATH</i> variable (see XBD <a href="../basedefs/V1_chap08.html#tag_08"><i>8. Environment Variables</i></a> ). The value in
73 the <i>FCEDIT</i> variable shall be used as a default when <b>-e</b> is not specified. If <i>FCEDIT</i> is null or unset, <a href=
74 "../utilities/ed.html"><i>ed</i></a> shall be used as the editor.</dd>
75 <dt><b>-l</b></dt>
76 <dd>(The letter ell.) List the commands rather than invoking an editor on them. The commands shall be written in the sequence
77 indicated by the <i>first</i> and <i>last</i> operands, as affected by <b>-r</b>, with each command preceded by the command
78 number.</dd>
79 <dt><b>-n</b></dt>
80 <dd>Suppress command numbers when listing with <b>-l</b>.</dd>
81 <dt><b>-r</b></dt>
82 <dd>Reverse the order of the commands listed (with <b>-l</b>) or edited (with neither <b>-l</b> nor <b>-s</b>).</dd>
83 <dt><b>-s</b></dt>
84 <dd>Re-execute the command without invoking an editor.</dd>
85 </dl>
86 </blockquote>
87 <h4 class="mansect"><a name="tag_20_44_05" id="tag_20_44_05"></a>OPERANDS</h4>
88 <blockquote>
89 <p>The following operands shall be supported:</p>
90 <dl compact>
91 <dd></dd>
92 <dt><i>first</i>, <i>last</i></dt>
93 <dd>Select the commands to list or edit. The number of previous commands that can be accessed shall be determined by the value of
94 the <i>HISTSIZE</i> variable. The value of <i>first</i> or <i>last</i> or both shall be one of the following:
95 <dl compact>
96 <dd></dd>
97 <dt><b>[+]</b><i>number</i></dt>
98 <dd>A positive number representing a command number; command numbers can be displayed with the <b>-l</b> option.</dd>
99 <dt><b>-</b><i>number</i></dt>
100 <dd>A negative decimal number representing the command that was executed <i>number</i> of commands previously. For example, -1 is
101 the immediately previous command.</dd>
102 <dt><i>string</i></dt>
103 <dd>A string indicating the most recently entered command that begins with that string. If the <i>old</i>=<i>new</i> operand is not
104 also specified with <b>-s</b>, the string form of the <i>first</i> operand cannot contain an embedded <equals-sign>.</dd>
105 </dl>
106 <p>When the synopsis form with <b>-s</b> is used:</p>
107 <ul>
108 <li>
109 <p>If <i>first</i> is omitted, the previous command shall be used.</p>
110 </li>
111 </ul>
112 <p>For the synopsis forms without <b>-s</b>:</p>
113 <ul>
114 <li>
115 <p>If <i>last</i> is omitted, <i>last</i> shall default to the previous command when <b>-l</b> is specified; otherwise, it shall
116 default to <i>first</i>.</p>
117 </li>
118 <li>
119 <p>If <i>first</i> and <i>last</i> are both omitted, the previous 16 commands shall be listed or the previous single command shall
120 be edited (based on the <b>-l</b> option).</p>
121 </li>
122 <li>
123 <p>If <i>first</i> and <i>last</i> are both present, all of the commands from <i>first</i> to <i>last</i> shall be edited (without
124 <b>-l</b>) or listed (with <b>-l</b>). Editing multiple commands shall be accomplished by presenting to the editor all of the
125 commands at one time, each command starting on a new line. If <i>first</i> represents a newer command than <i>last</i>, the
126 commands shall be listed or edited in reverse sequence, equivalent to using <b>-r</b>. For example, the following commands on the
127 first line are equivalent to the corresponding commands on the second:</p>
128 <pre>
129 <tt>fc -r 10 20 fc 30 40
130 fc 20 10 fc -r 40 30
131 </tt></pre></li>
132 <li>
133 <p>When a range of commands is used, it shall not be an error to specify <i>first</i> or <i>last</i> values that are not in the
134 history list; <i>fc</i> shall substitute the value representing the oldest or newest command in the list, as appropriate. For
135 example, if there are only ten commands in the history list, numbered 1 to 10:</p>
136 <pre>
137 <tt>fc -l
138 fc 1 99
139 </tt></pre>
140 <p>shall list and edit, respectively, all ten commands.</p>
141 </li>
142 </ul>
143 </dd>
144 <dt><i>old</i>=<i>new</i></dt>
145 <dd>Replace the first occurrence of string <i>old</i> in the commands to be re-executed by the string <i>new</i>.</dd>
146 </dl>
147 </blockquote>
148 <h4 class="mansect"><a name="tag_20_44_06" id="tag_20_44_06"></a>STDIN</h4>
149 <blockquote>
150 <p>Not used.</p>
151 </blockquote>
152 <h4 class="mansect"><a name="tag_20_44_07" id="tag_20_44_07"></a>INPUT FILES</h4>
153 <blockquote>
154 <p>None.</p>
155 </blockquote>
156 <h4 class="mansect"><a name="tag_20_44_08" id="tag_20_44_08"></a>ENVIRONMENT VARIABLES</h4>
157 <blockquote>
158 <p>The following environment variables shall affect the execution of <i>fc</i>:</p>
159 <dl compact>
160 <dd></dd>
161 <dt><i>FCEDIT</i></dt>
162 <dd>This variable, when expanded by the shell, shall determine the default value for the <b>-e</b> <i>editor</i> option's
163 <i>editor</i> option-argument. If <i>FCEDIT</i> is null or unset, <a href="../utilities/ed.html"><i>ed</i></a> shall be used as the
164 editor.</dd>
165 <dt><i>HISTFILE</i></dt>
166 <dd>Determine a pathname naming a command history file. If the <i>HISTFILE</i> variable is not set, the shell may attempt to access
167 or create a file <b>.sh_history</b> in the directory referred to by the <i>HOME</i> environment variable. If the shell cannot
168 obtain both read and write access to, or create, the history file, it shall use an unspecified mechanism that allows the history to
169 operate properly. (References to history "file" in this section shall be understood to mean this unspecified mechanism in such
170 cases.) An implementation may choose to access this variable only when initializing the history file; this initialization shall
171 occur when <i>fc</i> or <a href="../utilities/sh.html"><i>sh</i></a> first attempt to retrieve entries from, or add entries to, the
172 file, as the result of commands issued by the user, the file named by the <i>ENV</i> variable, or implementation-defined system
173 start-up files. In some historical shells, the history file is initialized just after the <i>ENV</i> file has been processed.
174 Therefore, it is implementation-defined whether changes made to <i>HISTFILE</i> after the history file has been initialized are
175 effective. Implementations may choose to disable the history list mechanism for users with appropriate privileges who do not set
176 <i>HISTFILE ;</i> the specific circumstances under which this occurs are implementation-defined. If more than one instance of the
177 shell is using the same history file, it is unspecified how updates to the history file from those shells interact. As entries are
178 deleted from the history file, they shall be deleted oldest first. It is unspecified when history file entries are physically
179 removed from the history file.</dd>
180 <dt><i>HISTSIZE</i></dt>
181 <dd>Determine a decimal number representing the limit to the number of previous commands that are accessible. If this variable is
182 unset, an unspecified default greater than or equal to 128 shall be used. The maximum number of commands in the history list is
183 unspecified, but shall be at least 128. An implementation may choose to access this variable only when initializing the history
184 file, as described under <i>HISTFILE .</i> Therefore, it is unspecified whether changes made to <i>HISTSIZE</i> after the history
185 file has been initialized are effective.</dd>
186 <dt><i>LANG</i></dt>
187 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
188 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
189 variables used to determine the values of locale categories.)</dd>
190 <dt><i>LC_ALL</i></dt>
191 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
192 <dt><i>LC_CTYPE</i></dt>
193 <dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
194 opposed to multi-byte characters in arguments and input files).</dd>
195 <dt><i>LC_MESSAGES</i></dt>
196 <dd><br>
197 Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.</dd>
198 <dt><i>NLSPATH</i></dt>
199 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">
200 Determine the location of messages objects and message catalogs. <img src="../images/opt-end.gif" alt="[Option End]" border=
201 "0"></dd>
202 </dl>
203 </blockquote>
204 <h4 class="mansect"><a name="tag_20_44_09" id="tag_20_44_09"></a>ASYNCHRONOUS EVENTS</h4>
205 <blockquote>
206 <p>Default.</p>
207 </blockquote>
208 <h4 class="mansect"><a name="tag_20_44_10" id="tag_20_44_10"></a>STDOUT</h4>
209 <blockquote>
210 <p>When the <b>-l</b> option is used to list commands, the format of each command in the list shall be as follows:</p>
211 <pre>
212 <tt>"%d\t%s\n", <</tt><i>line number</i><tt>>, <</tt><i>command</i><tt>>
213 </tt></pre>
214 <p>If both the <b>-l</b> and <b>-n</b> options are specified, the format of each command shall be:</p>
215 <pre>
216 <tt>"\t%s\n", <</tt><i>command</i><tt>>
217 </tt></pre>
218 <p>If the <<i>command</i>> consists of more than one line, the lines after the first shall be displayed as:</p>
219 <pre>
220 <tt>"\t%s\n", <</tt><i>continued-command</i><tt>>
221 </tt></pre></blockquote>
222 <h4 class="mansect"><a name="tag_20_44_11" id="tag_20_44_11"></a>STDERR</h4>
223 <blockquote>
224 <p>The standard error shall be used only for diagnostic messages.</p>
225 </blockquote>
226 <h4 class="mansect"><a name="tag_20_44_12" id="tag_20_44_12"></a>OUTPUT FILES</h4>
227 <blockquote>
228 <p>None.</p>
229 </blockquote>
230 <h4 class="mansect"><a name="tag_20_44_13" id="tag_20_44_13"></a>EXTENDED DESCRIPTION</h4>
231 <blockquote>
232 <p>None.</p>
233 </blockquote>
234 <h4 class="mansect"><a name="tag_20_44_14" id="tag_20_44_14"></a>EXIT STATUS</h4>
235 <blockquote>
236 <p>The following exit values shall be returned:</p>
237 <dl compact>
238 <dd></dd>
239 <dt> 0</dt>
240 <dd>Successful completion of the listing.</dd>
241 <dt>>0</dt>
242 <dd>An error occurred.</dd>
243 </dl>
244 <p>Otherwise, the exit status shall be that of the commands executed by <i>fc</i>.</p>
245 </blockquote>
246 <h4 class="mansect"><a name="tag_20_44_15" id="tag_20_44_15"></a>CONSEQUENCES OF ERRORS</h4>
247 <blockquote>
248 <p>Default.</p>
249 </blockquote>
250 <hr>
251 <div class="box"><em>The following sections are informative.</em></div>
252 <h4 class="mansect"><a name="tag_20_44_16" id="tag_20_44_16"></a>APPLICATION USAGE</h4>
253 <blockquote>
254 <p>This utility is required to be intrinsic. See <a href="../utilities/V3_chap01.html#tag_18_07"><i>1.7 Intrinsic Utilities</i></a>
255 for details.</p>
256 <p>Since editors sometimes use file descriptors as integral parts of their editing, redirecting their file descriptors as part of
257 the <i>fc</i> command can produce unexpected results. For example, if <a href="../utilities/vi.html"><i>vi</i></a> is the
258 <i>FCEDIT</i> editor, the command:</p>
259 <pre>
260 <tt>fc -s | more
261 </tt></pre>
262 <p>does not work correctly on many systems.</p>
263 <p>Users on windowing systems may want to have separate history files for each window by setting <i>HISTFILE</i> as follows:</p>
264 <pre>
265 <tt>HISTFILE=$HOME/.sh_hist$$
266 </tt></pre></blockquote>
267 <h4 class="mansect"><a name="tag_20_44_17" id="tag_20_44_17"></a>EXAMPLES</h4>
268 <blockquote>
269 <p>None.</p>
270 </blockquote>
271 <h4 class="mansect"><a name="tag_20_44_18" id="tag_20_44_18"></a>RATIONALE</h4>
272 <blockquote>
273 <p>This utility is based on the <i>fc</i> built-in of the KornShell.</p>
274 <p>An early proposal specified the <b>-e</b> option as <b>[-e</b> <i>editor</i> <b>[</b><i>old</i>= <i>new</i> <b>]]</b>, which is
275 not historical practice. Historical practice in <i>fc</i> of either <b>[-e</b> <i>editor</i><b>]</b> or <b>[-e - [</b> <i>old</i>=
276 <i>new</i> <b>]]</b> is acceptable, but not both together. To clarify this, a new option <b>-s</b> was introduced replacing the
277 <b>[-e -]</b>. This resolves the conflict and makes <i>fc</i> conform to the Utility Syntax Guidelines.</p>
278 <dl compact>
279 <dd></dd>
280 <dt><i>HISTFILE</i></dt>
281 <dd>Some implementations of the KornShell check for the superuser and do not create a history file unless <i>HISTFILE</i> is set.
282 This is done primarily to avoid creating unlinked files in the root file system when logging in during single-user mode.
283 <i>HISTFILE</i> must be set for the superuser to have history.</dd>
284 <dt><i>HISTSIZE</i></dt>
285 <dd>Needed to limit the size of history files. It is the intent of the standard developers that when two shells share the same
286 history file, commands that are entered in one shell shall be accessible by the other shell. Because of the difficulties of
287 synchronization over a network, the exact nature of the interaction is unspecified.</dd>
288 </dl>
289 <p>The initialization process for the history file can be dependent on the system start-up files, in that they may contain commands
290 that effectively preempt the settings the user has for <i>HISTFILE</i> and <i>HISTSIZE .</i> For example, function definition
291 commands are recorded in the history file. If the system administrator includes function definitions in some system start-up file
292 called before the <i>ENV</i> file, the history file is initialized before the user can influence its characteristics. In some
293 historical shells, the history file is initialized just after the <i>ENV</i> file has been processed. Because of these situations,
294 the text requires the initialization process to be implementation-defined.</p>
295 <p>Consideration was given to omitting the <i>fc</i> utility in favor of the command line editing feature in <a href=
296 "../utilities/sh.html"><i>sh</i></a>. For example, in <a href="../utilities/vi.html"><i>vi</i></a> editing mode, typing
297 <tt>"<ESC> v"</tt> is equivalent to:</p>
298 <pre>
299 <tt>EDITOR=vi fc
300 </tt></pre>
301 <p>However, the <i>fc</i> utility allows the user the flexibility to edit multiple commands simultaneously (such as <i>fc</i> 10
302 20) and to use editors other than those supported by <a href="../utilities/sh.html"><i>sh</i></a> for command line editing.</p>
303 <p>In the KornShell, the alias <b>r</b> ("re-do") is preset to <i>fc</i> <b>-e -</b> (equivalent to the POSIX <i>fc</i>
304 <b>-s</b>). This is probably an easier command name to remember than <i>fc</i> ("fix command"), but it does not meet the Utility
305 Syntax Guidelines. Renaming <i>fc</i> to <i>hist</i> or <i>redo</i> was considered, but since this description closely matches
306 historical KornShell practice already, such a renaming was seen as gratuitous. Users are free to create aliases whenever odd
307 historical names such as <i>fc</i>, <a href="../utilities/awk.html"><i>awk</i></a>, <a href="../utilities/cat.html"><i>cat</i></a>,
308 <a href="../utilities/grep.html"><i>grep</i></a>, or <a href="../utilities/yacc.html"><i>yacc</i></a> are standardized by
309 POSIX.</p>
310 <p>Command numbers have no ordering effects; they are like serial numbers. The <b>-r</b> option and -<i>number</i> operand address
311 the sequence of command execution, regardless of serial numbers. So, for example, if the command number wrapped back to 1 at some
312 arbitrary point, there would be no ambiguity associated with traversing the wrap point. For example, if the command history
313 were:</p>
314 <pre>
315 <tt>32766: echo 1
316 32767: echo 2
317 1: echo 3
318 </tt></pre>
319 <p>the number -2 refers to command 32767 because it is the second previous command, regardless of serial number.</p>
320 </blockquote>
321 <h4 class="mansect"><a name="tag_20_44_19" id="tag_20_44_19"></a>FUTURE DIRECTIONS</h4>
322 <blockquote>
323 <p>None.</p>
324 </blockquote>
325 <h4 class="mansect"><a name="tag_20_44_20" id="tag_20_44_20"></a>SEE ALSO</h4>
326 <blockquote>
327 <p><a href="../utilities/sh.html#"><i>sh</i></a></p>
328 <p>XBD <a href="../basedefs/V1_chap08.html#tag_08"><i>8. Environment Variables</i></a> , <a href=
329 "../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a></p>
330 </blockquote>
331 <h4 class="mansect"><a name="tag_20_44_21" id="tag_20_44_21"></a>CHANGE HISTORY</h4>
332 <blockquote>
333 <p>First released in Issue 4.</p>
334 </blockquote>
335 <h4 class="mansect"><a name="tag_20_44_22" id="tag_20_44_22"></a>Issue 5</h4>
336 <blockquote>
337 <p>The FUTURE DIRECTIONS section is added.</p>
338 </blockquote>
339 <h4 class="mansect"><a name="tag_20_44_23" id="tag_20_44_23"></a>Issue 6</h4>
340 <blockquote>
341 <p>This utility is marked as part of the User Portability Utilities option.</p>
342 <p>In the ENVIRONMENT VARIABLES section, the text "user's home directory" is updated to "directory referred to by the
343 <i>HOME</i> environment variable".</p>
344 </blockquote>
345 <h4 class="mansect"><a name="tag_20_44_24" id="tag_20_44_24"></a>Issue 7</h4>
346 <blockquote>
347 <p>SD5-XCU-ERN-97 is applied, updating the SYNOPSIS.</p>
348 </blockquote>
349 <h4 class="mansect"><a name="tag_20_44_25" id="tag_20_44_25"></a>Issue 8</h4>
350 <blockquote>
351 <p>Austin Group Defect 854 is applied, adding a note to the APPLICATION USAGE section that this utility is required to be
352 intrinsic.</p>
353 <p>Austin Group Defect 1122 is applied, changing the description of <i>NLSPATH .</i></p>
354 </blockquote>
355 <div class="box"><em>End of informative text.</em></div>
356 <hr>
357 <p> </p>
358 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
359 <hr size="2" noshade>
360 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
361 POSIX™ is a Trademark of The IEEE.<br>
362 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
363 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
364 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
365 ]</font></center>
366 <hr size="2" noshade>
367 <div class="NAVHEADER">
368 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
369 <tr class="nav">
370 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/false.html" accesskey="P"><<<
371 Previous</a></td>
372 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
373 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/fg.html" accesskey="N">Next >>></a></td>
374 </tr>
375 </table>
376 <hr align="left" width="100%"></div>
377 </body>
378 </html>