|
3294
|
1 @c Copyright (C) 1996, 1997 John W. Eaton |
|
|
2 @c This is part of the Octave manual. |
|
|
3 @c For copying conditions, see the file gpl.texi. |
|
|
4 |
|
|
5 @node Getting Started, Data Types, Introduction, Top |
|
|
6 @chapter Getting Started |
|
|
7 |
|
|
8 This chapter explains some of Octave's basic features, including how to |
|
|
9 start an Octave session, get help at the command prompt, edit the |
|
|
10 command line, and write Octave programs that can be executed as commands |
|
|
11 from your shell. |
|
|
12 |
|
|
13 @menu |
|
|
14 * Invoking Octave:: |
|
|
15 * Quitting Octave:: |
|
|
16 * Getting Help:: |
|
|
17 * Command Line Editing:: |
|
|
18 * Errors:: |
|
|
19 * Executable Octave Programs:: |
|
|
20 * Comments:: |
|
|
21 @end menu |
|
|
22 |
|
|
23 @node Invoking Octave, Quitting Octave, Getting Started, Getting Started |
|
|
24 @section Invoking Octave |
|
|
25 |
|
|
26 Normally, Octave is used interactively by running the program |
|
|
27 @samp{octave} without any arguments. Once started, Octave reads |
|
|
28 commands from the terminal until you tell it to exit. |
|
|
29 |
|
|
30 You can also specify the name of a file on the command line, and Octave |
|
|
31 will read and execute the commands from the named file and then exit |
|
|
32 when it is finished. |
|
|
33 |
|
|
34 You can further control how Octave starts by using the command-line |
|
|
35 options described in the next section, and Octave itself can remind you |
|
|
36 of the options available. Type @samp{octave --help} to display all |
|
|
37 available options and briefly describe their use (@samp{octave -h} is a |
|
|
38 shorter equivalent). |
|
|
39 |
|
|
40 @menu |
|
|
41 * Command Line Options:: |
|
|
42 * Startup Files:: |
|
|
43 @end menu |
|
|
44 |
|
|
45 @node Command Line Options, Startup Files, Invoking Octave, Invoking Octave |
|
|
46 @subsection Command Line Options |
|
|
47 @cindex Octave command options |
|
|
48 @cindex command options |
|
|
49 @cindex options, Octave command |
|
|
50 |
|
|
51 Here is a complete list of all the command line options that Octave |
|
|
52 accepts. |
|
|
53 |
|
|
54 @table @code |
|
|
55 @item --debug |
|
|
56 @itemx -d |
|
|
57 @cindex @code{--debug} |
|
|
58 @cindex @code{-d} |
|
|
59 Enter parser debugging mode. Using this option will cause Octave's |
|
|
60 parser to print a lot of information about the commands it reads, and is |
|
|
61 probably only useful if you are actually trying to debug the parser. |
|
|
62 |
|
|
63 @item --echo-commands |
|
|
64 @itemx -x |
|
|
65 @cindex @code{--echo-commands} |
|
|
66 @cindex @code{-x} |
|
|
67 Echo commands as they are executed. |
|
|
68 |
|
|
69 @item --exec-path @var{path} |
|
|
70 @cindex @code{--exec-path @var{path}} |
|
|
71 Specify the path to search for programs to run. The value of @var{path} |
|
|
72 specified on the command line will override any value of |
|
|
73 @code{OCTAVE_EXEC_PATH} found in the environment, but not any commands |
|
|
74 in the system or user startup files that set the built-in variable |
|
|
75 @code{EXEC_PATH}. |
|
|
76 |
|
|
77 @item --help |
|
|
78 @itemx -h |
|
|
79 @itemx -? |
|
|
80 @cindex @code{--help} |
|
|
81 @cindex @code{-h} |
|
|
82 @cindex @code{-?} |
|
|
83 Print short help message and exit. |
|
|
84 |
|
|
85 @item --info-file @var{filename} |
|
|
86 @cindex @code{--info-file @var{filename}} |
|
|
87 Specify the name of the info file to use. The value of @var{filename} |
|
|
88 specified on the command line will override any value of |
|
|
89 @code{OCTAVE_INFO_FILE} found in the environment, but not any commands |
|
|
90 in the system or user startup files that set the built-in variable |
|
|
91 @code{INFO_FILE}. |
|
|
92 |
|
|
93 @item --info-program @var{program} |
|
|
94 @cindex @code{--info-program @var{program}} |
|
|
95 Specify the name of the info program to use. The value of @var{program} |
|
|
96 specified on the command line will override any value of |
|
|
97 @code{OCTAVE_INFO_PROGRAM} found in the environment, but not any |
|
|
98 commands in the system or user startup files that set the built-in |
|
|
99 variable @code{INFO_PROGRAM}. |
|
|
100 |
|
|
101 @item --interactive |
|
|
102 @itemx -i |
|
|
103 @cindex @code{--interactive} |
|
|
104 @cindex @code{-i} |
|
|
105 Force interactive behavior. This can be useful for running Octave via a |
|
|
106 remote shell command or inside an Emacs shell buffer. For another way |
|
|
107 to run Octave within Emacs, see @ref{Emacs}. |
|
|
108 |
|
3428
|
109 @item --no-history |
|
|
110 @itemx -H |
|
|
111 Disable command-line history. |
|
|
112 |
|
3294
|
113 @item --no-init-file |
|
|
114 @cindex @code{--no-init-file} |
|
|
115 Don't read the @file{~/.octaverc} or @file{.octaverc} files. |
|
|
116 |
|
|
117 @item --no-line-editing |
|
|
118 @cindex @code{--no-line-editing} |
|
|
119 Disable command-line editing. |
|
|
120 |
|
|
121 @item --no-site-file |
|
|
122 @cindex @code{--no-site-file} |
|
|
123 Don't read the site-wide @file{octaverc} file. |
|
|
124 |
|
|
125 @item --norc |
|
|
126 @itemx -f |
|
|
127 @cindex @code{--norc} |
|
|
128 @cindex @code{-f} |
|
|
129 Don't read any of the system or user initialization files at startup. |
|
|
130 This is equivalent to using both of the options @code{--no-init-file} |
|
|
131 and @code{--no-site-file}. |
|
|
132 |
|
|
133 @item --path @var{path} |
|
|
134 @itemx -p @var{path} |
|
|
135 @cindex @code{--path @var{path}} |
|
|
136 @cindex @code{-p @var{path}} |
|
|
137 Specify the path to search for function files. The value of @var{path} |
|
|
138 specified on the command line will override any value of |
|
|
139 @code{OCTAVE_PATH} found in the environment, but not any commands in the |
|
|
140 system or user startup files that set the built-in variable @code{LOADPATH}. |
|
|
141 |
|
|
142 @item --silent |
|
|
143 @itemx --quiet |
|
|
144 @itemx -q |
|
|
145 @cindex @code{--silent} |
|
|
146 @cindex @code{--quiet} |
|
|
147 @cindex @code{-q} |
|
|
148 Don't print the usual greeting and version message at startup. |
|
|
149 |
|
|
150 @item --traditional |
|
|
151 @itemx --braindead |
|
|
152 @cindex @code{--traditional} |
|
|
153 @cindex @code{--braindead} |
|
|
154 Set initial values for user-preference variables to the following |
|
|
155 values for compatibility with @sc{Matlab}. |
|
|
156 |
|
|
157 @example |
|
|
158 PS1 = ">> " |
|
|
159 PS2 = "" |
|
|
160 beep_on_error = 1 |
|
|
161 default_save_format = "mat-binary" |
|
|
162 define_all_return_values = 1 |
|
|
163 do_fortran_indexing = 1 |
|
|
164 crash_dumps_octave_core = 0 |
|
|
165 empty_list_elements_ok = 1 |
|
|
166 implicit_str_to_num_ok = 1 |
|
|
167 ok_to_lose_imaginary_part = 1 |
|
|
168 page_screen_output = 0 |
|
|
169 prefer_column_vectors = 0 |
|
|
170 print_empty_dimensions = 0 |
|
|
171 treat_neg_dim_as_zero = 1 |
|
|
172 warn_function_name_clash = 0 |
|
|
173 whitespace_in_literal_matrix = "traditional" |
|
|
174 @end example |
|
|
175 |
|
|
176 @item --verbose |
|
|
177 @itemx -V |
|
|
178 @cindex @code{--verbose} |
|
|
179 @cindex @code{-V} |
|
|
180 Turn on verbose output. |
|
|
181 |
|
|
182 @item --version |
|
|
183 @itemx -v |
|
|
184 @cindex @code{--version} |
|
|
185 @cindex @code{-v} |
|
|
186 Print the program version number and exit. |
|
|
187 |
|
|
188 @item @var{file} |
|
|
189 Execute commands from @var{file}. |
|
|
190 @end table |
|
|
191 |
|
|
192 Octave also includes several built-in variables that contain information |
|
|
193 about the command line, including the number of arguments and all of the |
|
|
194 options. |
|
|
195 |
|
3332
|
196 @DOCSTRING(argv) |
|
3294
|
197 |
|
3332
|
198 @DOCSTRING(program_invocation_name) |
|
3294
|
199 |
|
|
200 Here is an example of using these variables to reproduce Octave's |
|
|
201 command line. |
|
|
202 |
|
|
203 @example |
|
|
204 printf ("%s", program_name); |
|
|
205 for i = 1:nargin |
|
|
206 printf (" %s", argv(i)); |
|
|
207 endfor |
|
|
208 printf ("\n"); |
|
|
209 @end example |
|
|
210 |
|
|
211 @noindent |
|
3402
|
212 @xref{Index Expressions}, for an explanation of how to properly index |
|
|
213 arrays of strings and substrings in Octave, and @xref{Defining Functions}, |
|
3294
|
214 for information about the variable @code{nargin}. |
|
|
215 |
|
|
216 @node Startup Files, , Command Line Options, Invoking Octave |
|
|
217 @subsection Startup Files |
|
|
218 @cindex initialization |
|
|
219 @cindex startup |
|
|
220 |
|
|
221 When Octave starts, it looks for commands to execute from the following |
|
|
222 files: |
|
|
223 |
|
|
224 @cindex startup files |
|
|
225 |
|
|
226 @table @code |
|
|
227 @item @var{octave-home}/share/octave/site/m/startup/octaverc |
|
|
228 Where @var{octave-home} is the directory in which all of Octave is |
|
|
229 installed (the default is @file{@value{OCTAVEHOME}}). This file is |
|
|
230 provided so that changes to the default Octave environment can be made |
|
|
231 globally for all users at your site for all versions of Octave you have |
|
|
232 installed. Some care should be taken when making changes to this file, |
|
|
233 since all users of Octave at your site will be affected. |
|
|
234 |
|
|
235 @item @var{octave-home}/share/octave/@var{version}/m/startup/octaverc |
|
|
236 Where @var{octave-home} is the directory in which all of Octave is |
|
|
237 installed (the default is @file{@value{OCTAVEHOME}}), and @var{version} |
|
|
238 is the version number of Octave. This file is provided so that changes |
|
|
239 to the default Octave environment can be made globally for all users for |
|
|
240 a particular version of Octave. Some care should be taken when making |
|
|
241 changes to this file, since all users of Octave at your site will be |
|
|
242 affected. |
|
|
243 |
|
|
244 @item ~/.octaverc |
|
|
245 @cindex @code{~/.octaverc} |
|
|
246 This file is normally used to make personal changes to the default |
|
|
247 Octave environment. |
|
|
248 |
|
|
249 @item .octaverc |
|
|
250 @cindex @code{.octaverc} |
|
|
251 This file can be used to make changes to the default Octave environment |
|
|
252 for a particular project. Octave searches for this file in the current |
|
|
253 directory after it reads @file{~/.octaverc}. Any use of the @code{cd} |
|
|
254 command in the @file{~/.octaverc} file will affect the directory that |
|
|
255 Octave searches for the file @file{.octaverc}. |
|
|
256 |
|
|
257 If you start Octave in your home directory, commands from from the file |
|
|
258 @file{~/.octaverc} will only be executed once. |
|
|
259 @end table |
|
|
260 |
|
|
261 A message will be displayed as each of the startup files is read if you |
|
|
262 invoke Octave with the @code{--verbose} option but without the |
|
|
263 @code{--silent} option. |
|
|
264 |
|
|
265 Startup files may contain any valid Octave commands, including function |
|
|
266 definitions. |
|
|
267 |
|
|
268 @node Quitting Octave, Getting Help, Invoking Octave, Getting Started |
|
|
269 @section Quitting Octave |
|
|
270 @cindex exiting octave |
|
|
271 @cindex quitting octave |
|
|
272 |
|
3332
|
273 @DOCSTRING(quit) |
|
3294
|
274 |
|
3332
|
275 @DOCSTRING(atexit) |
|
3294
|
276 |
|
|
277 @node Getting Help, Command Line Editing, Quitting Octave, Getting Started |
|
|
278 @section Commands for Getting Help |
|
|
279 @cindex on-line help |
|
|
280 @cindex help, on-line |
|
|
281 |
|
|
282 The entire text of this manual is available from the Octave prompt |
|
|
283 via the command @kbd{help -i}. In addition, the documentation for |
|
|
284 individual user-written functions and variables is also available via |
|
|
285 the @kbd{help} command. This section describes the commands used for |
|
|
286 reading the manual and the documentation strings for user-supplied |
|
|
287 functions and variables. @xref{Function Files}, for more information |
|
|
288 about how to document the functions you write. |
|
|
289 |
|
3332
|
290 @DOCSTRING(help) |
|
3294
|
291 |
|
|
292 The help command can give you information about operators, but not the |
|
|
293 comma and semicolons that are used as command separators. To get help |
|
|
294 for those, you must type @kbd{help comma} or @kbd{help semicolon}. |
|
|
295 |
|
3332
|
296 @DOCSTRING(INFO_FILE) |
|
3294
|
297 |
|
3332
|
298 @DOCSTRING(INFO_PROGRAM) |
|
3294
|
299 |
|
3332
|
300 @DOCSTRING(suppress_verbose_help_message) |
|
3294
|
301 |
|
|
302 @node Command Line Editing, Errors, Getting Help, Getting Started |
|
|
303 @section Command Line Editing |
|
|
304 @cindex command-line editing |
|
|
305 @cindex editing the command line |
|
|
306 |
|
|
307 Octave uses the GNU readline library to provide an extensive set of |
|
|
308 command-line editing and history features. Only the most common |
|
|
309 features are described in this manual. Please see The GNU Readline |
|
|
310 Library manual for more information. |
|
|
311 |
|
|
312 To insert printing characters (letters, digits, symbols, etc.), simply |
|
|
313 type the character. Octave will insert the character at the cursor and |
|
|
314 advance the cursor forward. |
|
|
315 |
|
|
316 Many of the command-line editing functions operate using control |
|
|
317 characters. For example, the character @kbd{Control-a} moves the cursor |
|
|
318 to the beginning of the line. To type @kbd{C-a}, hold down @key{CTRL} |
|
|
319 and then press @key{a}. In the following sections, control characters |
|
|
320 such as @kbd{Control-a} are written as @kbd{C-a}. |
|
|
321 |
|
|
322 Another set of command-line editing functions use Meta characters. On |
|
|
323 some terminals, you type @kbd{M-u} by holding down @key{META} and |
|
|
324 pressing @key{u}. If your terminal does not have a @key{META} key, you |
|
|
325 can still type Meta charcters using two-character sequences starting |
|
|
326 with @kbd{ESC}. Thus, to enter @kbd{M-u}, you could type |
|
|
327 @key{ESC}@key{u}. The @kbd{ESC} character sequences are also allowed on |
|
|
328 terminals with real Meta keys. In the following sections, Meta |
|
|
329 characters such as @kbd{Meta-u} are written as @kbd{M-u}. |
|
|
330 |
|
3428
|
331 |
|
3294
|
332 @menu |
|
|
333 * Cursor Motion:: |
|
|
334 * Killing and Yanking:: |
|
|
335 * Commands For Text:: |
|
|
336 * Commands For Completion:: |
|
|
337 * Commands For History:: |
|
3428
|
338 * Customizing @code{readline}:: |
|
3294
|
339 * Customizing the Prompt:: |
|
|
340 * Diary and Echo Commands:: |
|
|
341 @end menu |
|
|
342 |
|
|
343 @node Cursor Motion, Killing and Yanking, Command Line Editing, Command Line Editing |
|
|
344 @subsection Cursor Motion |
|
|
345 |
|
|
346 The following commands allow you to position the cursor. |
|
|
347 |
|
|
348 @table @kbd |
|
|
349 @item C-b |
|
|
350 Move back one character. |
|
|
351 |
|
|
352 @item C-f |
|
|
353 Move forward one character. |
|
|
354 |
|
|
355 @item @key{DEL} |
|
|
356 Delete the character to the left of the cursor. |
|
|
357 |
|
|
358 @item C-d |
|
|
359 Delete the character underneath the cursor. |
|
|
360 |
|
|
361 @item M-f |
|
|
362 Move forward a word. |
|
|
363 |
|
|
364 @item M-b |
|
|
365 Move backward a word. |
|
|
366 |
|
|
367 @item C-a |
|
|
368 Move to the start of the line. |
|
|
369 |
|
|
370 @item C-e |
|
|
371 Move to the end of the line. |
|
|
372 |
|
|
373 @item C-l |
|
|
374 Clear the screen, reprinting the current line at the top. |
|
|
375 |
|
|
376 @item C-_ |
|
|
377 @itemx C-/ |
|
|
378 Undo the last thing that you did. You can undo all the way back to an |
|
|
379 empty line. |
|
|
380 |
|
|
381 @item M-r |
|
|
382 Undo all changes made to this line. This is like typing the `undo' |
|
|
383 command enough times to get back to the beginning. |
|
|
384 @end table |
|
|
385 |
|
|
386 The above table describes the most basic possible keystrokes that you need |
|
|
387 in order to do editing of the input line. On most terminals, you can |
|
|
388 also use the arrow keys in place of @kbd{C-f} and @kbd{C-b} to move |
|
|
389 forward and backward. |
|
|
390 |
|
|
391 Notice how @kbd{C-f} moves forward a character, while @kbd{M-f} moves |
|
|
392 forward a word. It is a loose convention that control keystrokes |
|
|
393 operate on characters while meta keystrokes operate on words. |
|
|
394 |
|
|
395 There is also a function available so that you can clear the screen from |
|
|
396 within Octave programs. |
|
|
397 |
|
|
398 @cindex clearing the screen |
|
|
399 |
|
3332
|
400 @DOCSTRING(clc) |
|
3294
|
401 |
|
|
402 @node Killing and Yanking, Commands For Text, Cursor Motion, Command Line Editing |
|
|
403 @subsection Killing and Yanking |
|
|
404 |
|
|
405 @dfn{Killing} text means to delete the text from the line, but to save |
|
|
406 it away for later use, usually by @dfn{yanking} it back into the line. |
|
|
407 If the description for a command says that it `kills' text, then you can |
|
|
408 be sure that you can get the text back in a different (or the same) |
|
|
409 place later. |
|
|
410 |
|
|
411 Here is the list of commands for killing text. |
|
|
412 |
|
|
413 @table @kbd |
|
|
414 @item C-k |
|
|
415 Kill the text from the current cursor position to the end of the line. |
|
|
416 |
|
|
417 @item M-d |
|
|
418 Kill from the cursor to the end of the current word, or if between |
|
|
419 words, to the end of the next word. |
|
|
420 |
|
|
421 @item M-@key{DEL} |
|
|
422 Kill from the cursor to the start of the previous word, or if between |
|
|
423 words, to the start of the previous word. |
|
|
424 |
|
|
425 @item C-w |
|
|
426 Kill from the cursor to the previous whitespace. This is different than |
|
|
427 @kbd{M-@key{DEL}} because the word boundaries differ. |
|
|
428 @end table |
|
|
429 |
|
|
430 And, here is how to @dfn{yank} the text back into the line. Yanking |
|
|
431 means to copy the most-recently-killed text from the kill buffer. |
|
|
432 |
|
|
433 @table @kbd |
|
|
434 @item C-y |
|
|
435 Yank the most recently killed text back into the buffer at the cursor. |
|
|
436 |
|
|
437 @item M-y |
|
|
438 Rotate the kill-ring, and yank the new top. You can only do this if |
|
|
439 the prior command is @kbd{C-y} or @kbd{M-y}. |
|
|
440 @end table |
|
|
441 |
|
|
442 When you use a kill command, the text is saved in a @dfn{kill-ring}. |
|
|
443 Any number of consecutive kills save all of the killed text together, so |
|
|
444 that when you yank it back, you get it in one clean sweep. The kill |
|
|
445 ring is not line specific; the text that you killed on a previously |
|
|
446 typed line is available to be yanked back later, when you are typing |
|
|
447 another line. |
|
|
448 |
|
|
449 @node Commands For Text, Commands For Completion, Killing and Yanking, Command Line Editing |
|
|
450 @subsection Commands For Changing Text |
|
|
451 |
|
|
452 The following commands can be used for entering characters that would |
|
|
453 otherwise have a special meaning (e.g., @kbd{TAB}, @kbd{C-q}, etc.), or |
|
|
454 for quickly correcting typing mistakes. |
|
|
455 |
|
|
456 @table @kbd |
|
|
457 @item C-q |
|
|
458 @itemx C-v |
|
|
459 Add the next character that you type to the line verbatim. This is |
|
|
460 how to insert things like @kbd{C-q} for example. |
|
|
461 |
|
|
462 @item M-@key{TAB} |
|
|
463 Insert a tab character. |
|
|
464 |
|
|
465 @item C-t |
|
|
466 Drag the character before the cursor forward over the character at the |
|
|
467 cursor, also moving the cursor forward. If the cursor is at the end of |
|
|
468 the line, then transpose the two characters before it. |
|
|
469 |
|
|
470 @item M-t |
|
|
471 Drag the word behind the cursor past the word in front of the cursor |
|
|
472 moving the cursor over that word as well. |
|
|
473 |
|
|
474 @item M-u |
|
|
475 Uppercase the characters following the cursor to the end of the current |
|
|
476 (or following) word, moving the cursor to the end of the word. |
|
|
477 |
|
|
478 @item M-l |
|
|
479 Lowecase the characters following the cursor to the end of the current |
|
|
480 (or following) word, moving the cursor to the end of the word. |
|
|
481 |
|
|
482 @item M-c |
|
|
483 Uppercase the character following the cursor (or the beginning of the |
|
|
484 next word if the cursor is between words), moving the cursor to the end |
|
|
485 of the word. |
|
|
486 @end table |
|
|
487 |
|
|
488 @node Commands For Completion, Commands For History, Commands For Text, Command Line Editing |
|
|
489 @subsection Letting Readline Type For You |
|
|
490 @cindex command completion |
|
|
491 |
|
|
492 The following commands allow Octave to complete command and variable |
|
|
493 names for you. |
|
|
494 |
|
|
495 @table @kbd |
|
|
496 @item @key{TAB} |
|
|
497 Attempt to do completion on the text before the cursor. Octave can |
|
|
498 complete the names of commands and variables. |
|
|
499 |
|
|
500 @item M-? |
|
|
501 List the possible completions of the text before the cursor. |
|
|
502 @end table |
|
|
503 |
|
3332
|
504 @DOCSTRING(completion_append_char) |
|
3294
|
505 |
|
3332
|
506 @DOCSTRING(completion_matches) |
|
3294
|
507 |
|
3428
|
508 @node Commands For History, Customizing @code{readline}, Commands For Completion, Command Line Editing |
|
3294
|
509 @subsection Commands For Manipulating The History |
|
|
510 @cindex command history |
|
|
511 @cindex input history |
|
|
512 @cindex history of commands |
|
|
513 |
|
|
514 Octave normally keeps track of the commands you type so that you can |
|
|
515 recall previous commands to edit or execute them again. When you exit |
|
|
516 Octave, the most recent commands you have typed, up to the number |
|
|
517 specified by the variable @code{history_size}, are saved in a file. |
|
|
518 When Octave starts, it loads an initial list of commands from the file |
|
|
519 named by the variable @code{history_file}. |
|
|
520 |
|
|
521 Here are the commands for simple browsing and searching the history |
|
|
522 list. |
|
|
523 |
|
|
524 @table @kbd |
|
|
525 @item @key{LFD} |
|
|
526 @itemx @key{RET} |
|
|
527 Accept the line regardless of where the cursor is. If this line is |
|
|
528 non-empty, add it to the history list. If this line was a history |
|
|
529 line, then restore the history line to its original state. |
|
|
530 |
|
|
531 @item C-p |
|
|
532 Move `up' through the history list. |
|
|
533 |
|
|
534 @item C-n |
|
|
535 Move `down' through the history list. |
|
|
536 |
|
|
537 @item M-< |
|
|
538 Move to the first line in the history. |
|
|
539 |
|
|
540 @item M-> |
|
|
541 Move to the end of the input history, i.e., the line you are entering! |
|
|
542 |
|
|
543 @item C-r |
|
|
544 Search backward starting at the current line and moving `up' through |
|
|
545 the history as necessary. This is an incremental search. |
|
|
546 |
|
|
547 @item C-s |
|
|
548 Search forward starting at the current line and moving `down' through |
|
|
549 the history as necessary. |
|
|
550 @end table |
|
|
551 |
|
|
552 On most terminals, you can also use the arrow keys in place of @kbd{C-p} |
|
|
553 and @kbd{C-n} to move through the history list. |
|
|
554 |
|
|
555 In addition to the keyboard commands for moving through the history |
|
|
556 list, Octave provides three functions for viewing, editing, and |
|
|
557 re-running chunks of commands from the history list. |
|
|
558 |
|
3332
|
559 @DOCSTRING(history) |
|
3294
|
560 |
|
3332
|
561 @DOCSTRING(edit_history) |
|
3294
|
562 |
|
3332
|
563 @DOCSTRING(run_history) |
|
3294
|
564 |
|
3368
|
565 @DOCSTRING(EDITOR) |
|
3294
|
566 |
|
3332
|
567 @DOCSTRING(history_file) |
|
3294
|
568 |
|
3332
|
569 @DOCSTRING(history_size) |
|
3294
|
570 |
|
3332
|
571 @DOCSTRING(saving_history) |
|
3294
|
572 |
|
3428
|
573 @node Customizing @code{readline}, Customizing the Prompt, Commands For History, Command Line Editing |
|
|
574 @subsection Customizing @code{readline} |
|
|
575 |
|
|
576 @c XXX FIXME XXX -- need a brief description of the ~/.inputrc file here. |
|
|
577 |
|
|
578 @DOCSTRING{read_readline_init_file} |
|
|
579 |
|
|
580 @node Customizing the Prompt, Diary and Echo Commands, Customizing @code{readline}, Command Line Editing |
|
3294
|
581 @subsection Customizing the Prompt |
|
|
582 @cindex prompt customization |
|
|
583 @cindex customizing the prompt |
|
|
584 |
|
|
585 The following variables are available for customizing the appearance of |
|
|
586 the command-line prompts. Octave allows the prompt to be customized by |
|
|
587 inserting a number of backslash-escaped special characters that are |
|
|
588 decoded as follows: |
|
|
589 |
|
|
590 @table @samp |
|
|
591 @item \t |
|
|
592 The time. |
|
|
593 |
|
|
594 @item \d |
|
|
595 The date. |
|
|
596 |
|
|
597 @item \n |
|
|
598 Begins a new line by printing the equivalent of a carriage return |
|
|
599 followed by a line feed. |
|
|
600 |
|
|
601 @item \s |
|
|
602 The name of the program (usually just @samp{octave}). |
|
|
603 |
|
|
604 @item \w |
|
|
605 The current working directory. |
|
|
606 |
|
|
607 @item \W |
|
|
608 The basename of the current working directory. |
|
|
609 |
|
|
610 @item \u |
|
|
611 The username of the current user. |
|
|
612 |
|
|
613 @item \h |
|
|
614 The hostname, up to the first `.'. |
|
|
615 |
|
|
616 @item \H |
|
|
617 The hostname. |
|
|
618 |
|
|
619 @item \# |
|
|
620 The command number of this command, counting from when Octave starts. |
|
|
621 |
|
|
622 @item \! |
|
|
623 The history number of this command. This differs from @samp{\#} by the |
|
|
624 number of commands in the history list when Octave starts. |
|
|
625 |
|
|
626 @item \$ |
|
|
627 If the effective UID is 0, a @samp{#}, otherwise a @samp{$}. |
|
|
628 |
|
|
629 @item \nnn |
|
|
630 The character whose character code in octal is @var{nnn}. |
|
|
631 |
|
|
632 @item \\ |
|
|
633 A backslash. |
|
|
634 @end table |
|
|
635 |
|
3332
|
636 @DOCSTRING(PS1) |
|
3294
|
637 |
|
3332
|
638 @DOCSTRING(PS2) |
|
3294
|
639 |
|
3332
|
640 @DOCSTRING(PS4) |
|
3294
|
641 |
|
|
642 @node Diary and Echo Commands, , Customizing the Prompt, Command Line Editing |
|
|
643 @subsection Diary and Echo Commands |
|
|
644 @cindex diary of commands and output |
|
|
645 @cindex command and ouput logs |
|
|
646 @cindex logging commands and output |
|
|
647 @cindex echoing executing commands |
|
|
648 @cindex command echoing |
|
|
649 |
|
|
650 Octave's diary feature allows you to keep a log of all or part of an |
|
|
651 interactive session by recording the input you type and the output that |
|
|
652 Octave produces in a separate file. |
|
|
653 |
|
3332
|
654 @DOCSTRING(diary) |
|
3294
|
655 |
|
|
656 Sometimes it is useful to see the commands in a function or script as |
|
|
657 they are being evaluated. This can be especially helpful for debugging |
|
|
658 some kinds of problems. |
|
|
659 |
|
3332
|
660 @DOCSTRING(echo) |
|
3294
|
661 |
|
3332
|
662 @DOCSTRING(echo_executing_commands) |
|
3294
|
663 |
|
|
664 @node Errors, Executable Octave Programs, Command Line Editing, Getting Started |
|
|
665 @section How Octave Reports Errors |
|
|
666 @cindex error messages |
|
|
667 @cindex messages, error |
|
|
668 |
|
|
669 Octave reports two kinds of errors for invalid programs. |
|
|
670 |
|
|
671 A @dfn{parse error} occurs if Octave cannot understand something you |
|
|
672 have typed. For example, if you misspell a keyword, |
|
|
673 |
|
|
674 @example |
|
|
675 octave:13> functon y = f (x) y = x^2; endfunction |
|
|
676 @end example |
|
|
677 |
|
|
678 @noindent |
|
|
679 Octave will respond immediately with a message like this: |
|
|
680 |
|
|
681 @example |
|
|
682 parse error: |
|
|
683 |
|
|
684 functon y = f (x) y = x^2; endfunction |
|
|
685 ^ |
|
|
686 @end example |
|
|
687 |
|
|
688 @noindent |
|
|
689 For most parse errors, Octave uses a caret (@samp{^}) to mark the point |
|
|
690 on the line where it was unable to make sense of your input. In this |
|
|
691 case, Octave generated an error message because the keyword |
|
|
692 @code{function} was misspelled. Instead of seeing @samp{function f}, |
|
|
693 Octave saw two consecutive variable names, which is invalid in this |
|
|
694 context. It marked the error at @code{y} because the first name by |
|
|
695 itself was accepted as valid input. |
|
|
696 |
|
|
697 Another class of error message occurs at evaluation time. These |
|
|
698 errors are called @dfn{run-time errors}, or sometimes |
|
|
699 @dfn{evaluation errors} because they occur when your program is being |
|
|
700 @dfn{run}, or @dfn{evaluated}. For example, if after correcting the |
|
|
701 mistake in the previous function definition, you type |
|
|
702 |
|
|
703 @example |
|
|
704 octave:13> f () |
|
|
705 @end example |
|
|
706 |
|
|
707 @noindent |
|
|
708 Octave will respond with |
|
|
709 |
|
|
710 @example |
|
|
711 @group |
|
|
712 error: `x' undefined near line 1 column 24 |
|
|
713 error: evaluating expression near line 1, column 24 |
|
|
714 error: evaluating assignment expression near line 1, column 22 |
|
|
715 error: called from `f' |
|
|
716 @end group |
|
|
717 @end example |
|
|
718 |
|
|
719 This error message has several parts, and gives you quite a bit of |
|
|
720 information to help you locate the source of the error. The messages |
|
|
721 are generated from the point of the innermost error, and provide a |
|
|
722 traceback of enclosing expressions and function calls. |
|
|
723 |
|
|
724 In the example above, the first line indicates that a variable named |
|
|
725 @samp{x} was found to be undefined near line 1 and column 24 of some |
|
|
726 function or expression. For errors occurring within functions, lines |
|
|
727 are counted from the beginning of the file containing the function |
|
|
728 definition. For errors occurring at the top level, the line number |
|
|
729 indicates the input line number, which is usually displayed in the |
|
|
730 prompt string. |
|
|
731 |
|
|
732 The second and third lines in the example indicate that the error |
|
|
733 occurred within an assignment expression, and the last line of the error |
|
|
734 message indicates that the error occurred within the function @code{f}. |
|
|
735 If the function @code{f} had been called from another function, for |
|
|
736 example, @code{g}, the list of errors would have ended with one more |
|
|
737 line: |
|
|
738 |
|
|
739 @example |
|
|
740 error: called from `g' |
|
|
741 @end example |
|
|
742 |
|
|
743 These lists of function calls usually make it fairly easy to trace the |
|
|
744 path your program took before the error occurred, and to correct the |
|
|
745 error before trying again. |
|
|
746 |
|
|
747 @node Executable Octave Programs, Comments, Errors, Getting Started |
|
|
748 @section Executable Octave Programs |
|
|
749 @cindex executable scripts |
|
|
750 @cindex scripts |
|
|
751 @cindex self contained programs |
|
|
752 @cindex program, self contained |
|
|
753 @cindex @samp{#!} |
|
|
754 |
|
|
755 Once you have learned Octave, you may want to write self-contained |
|
|
756 Octave scripts, using the @samp{#!} script mechanism. You can do this |
|
|
757 on GNU systems and on many Unix systems @footnote{The @samp{#!} |
|
|
758 mechanism works on Unix systems derived from Berkeley Unix, System V |
|
|
759 Release 4, and some System V Release 3 systems.} |
|
|
760 |
|
|
761 For example, you could create a text file named @file{hello}, containing |
|
|
762 the following lines: |
|
|
763 |
|
|
764 @example |
|
|
765 @group |
|
|
766 #! @var{octave-interpreter-name} -qf |
|
|
767 # a sample Octave program |
|
|
768 printf ("Hello, world!\n"); |
|
|
769 @end group |
|
|
770 @end example |
|
|
771 |
|
|
772 @noindent |
|
|
773 (where @var{octave-interpreter-name} should be replaced with the full |
|
|
774 file name for your Octave binary). After making this file executable |
|
|
775 (with the @code{chmod} command), you can simply type: |
|
|
776 |
|
|
777 @example |
|
|
778 hello |
|
|
779 @end example |
|
|
780 |
|
|
781 @noindent |
|
|
782 at the shell, and the system will arrange to run Octave as if you had |
|
|
783 typed: |
|
|
784 |
|
|
785 @example |
|
|
786 octave hello |
|
|
787 @end example |
|
|
788 |
|
|
789 The line beginning with @samp{#!} lists the full file name of an |
|
|
790 interpreter to be run, and an optional initial command line argument to |
|
|
791 pass to that interpreter. The operating system then runs the |
|
|
792 interpreter with the given argument and the full argument list of the |
|
|
793 executed program. The first argument in the list is the full file name |
|
|
794 of the Octave program. The rest of the argument list will either be |
|
|
795 options to Octave, or data files, or both. The @samp{-qf} option is |
|
|
796 usually specified in stand-alone Octave programs to prevent them from |
|
|
797 printing the normal startup message, and to keep them from behaving |
|
|
798 differently depending on the contents of a particular user's |
|
|
799 @file{~/.octaverc} file. @xref{Invoking Octave}. Note that some |
|
|
800 operating systems may place a limit on the number of characters that are |
|
|
801 recognized after @samp{#!}. |
|
|
802 |
|
|
803 Self-contained Octave scripts are useful when you want to write a |
|
|
804 program which users can invoke without knowing that the program is |
|
|
805 written in the Octave language. |
|
|
806 |
|
|
807 If you invoke an executable Octave script with command line arguments, |
|
|
808 the arguments are available in the built-in variable @code{argv}. |
|
|
809 @xref{Command Line Options}. For example, the following program will |
|
|
810 reproduce the command line that is used to execute it. |
|
|
811 |
|
|
812 @example |
|
|
813 @group |
|
|
814 #! /bin/octave -qf |
|
|
815 printf ("%s", program_name); |
|
|
816 for i = 1:nargin |
|
|
817 printf (" %s", argv(i,:)); |
|
|
818 endfor |
|
|
819 printf ("\n"); |
|
|
820 @end group |
|
|
821 @end example |
|
|
822 |
|
|
823 @node Comments, , Executable Octave Programs, Getting Started |
|
|
824 @section Comments in Octave Programs |
|
|
825 @cindex @samp{#} |
|
|
826 @cindex @samp{%} |
|
|
827 @cindex comments |
|
|
828 @cindex use of comments |
|
|
829 @cindex documenting Octave programs |
|
|
830 @cindex programs |
|
|
831 |
|
|
832 A @dfn{comment} is some text that is included in a program for the sake |
|
|
833 of human readers, and that is not really part of the program. Comments |
|
|
834 can explain what the program does, and how it works. Nearly all |
|
|
835 programming languages have provisions for comments, because programs are |
|
|
836 typically hard to understand without them. |
|
|
837 |
|
|
838 In the Octave language, a comment starts with either the sharp sign |
|
|
839 character, @samp{#}, or the percent symbol @samp{%} and continues to the |
|
|
840 end of the line. The Octave interpreter ignores the rest of a |
|
|
841 line following a sharp sign or percent symbol. For example, we could |
|
|
842 have put the following into the function @code{f}: |
|
|
843 |
|
|
844 @example |
|
|
845 @group |
|
|
846 function xdot = f (x, t) |
|
|
847 |
|
|
848 # usage: f (x, t) |
|
|
849 # |
|
|
850 # This function defines the right hand |
|
|
851 # side functions for a set of nonlinear |
|
|
852 # differential equations. |
|
|
853 |
|
|
854 r = 0.25; |
|
|
855 @dots{} |
|
|
856 endfunction |
|
|
857 @end group |
|
|
858 @end example |
|
|
859 |
|
|
860 The @code{help} command (@pxref{Getting Help}) is able to find the first |
|
|
861 block of comments in a function (even those that are composed directly |
|
|
862 on the command line). This means that users of Octave can use the same |
|
|
863 commands to get help for built-in functions, and for functions that you |
|
|
864 have defined. For example, after defining the function @code{f} above, |
|
|
865 the command @kbd{help f} produces the output |
|
|
866 |
|
|
867 @example |
|
|
868 @group |
|
|
869 usage: f (x, t) |
|
|
870 |
|
|
871 This function defines the right hand |
|
|
872 side functions for a set of nonlinear |
|
|
873 differential equations. |
|
|
874 @end group |
|
|
875 @end example |
|
|
876 |
|
|
877 Although it is possible to put comment lines into keyboard-composed |
|
|
878 throw-away Octave programs, it usually isn't very useful, because the |
|
|
879 purpose of a comment is to help you or another person understand the |
|
|
880 program at a later time. |
|
|
881 |
