Major mode for editing Octave code.
This mode makes it easier to write Octave code by helping with
indentation, doing some of the typing for you (with Abbrev mode) and by
showing keywords, comments, strings, etc. in different faces (with
Font Lock mode on terminals that support it).
Octave itself is a high-level language, primarily intended for numerical
computations. It provides a convenient command line interface for
solving linear and nonlinear problems numerically. Function definitions
can also be stored in files, and it can be used in a batch mode (which
is why you need this mode!).
The latest released version of Octave is always available via anonymous
ftp from ftp.octave.org in the directory `/pub/octave'. Complete
source and binaries for several popular systems are available.
Type M-x list-abbrevs to display the built-in abbrevs for Octave keywords.
Uses keymap `octave-mode-map', which is not currently defined.
Variables you can use to customize Octave mode
Non-nil means show matching begin of block when inserting a space,
newline or semicolon after an else or end keyword. Default is t.
Extra indentation applied to statements in block structures.
Default is 2.
Extra indentation applied to Octave continuation lines.
Default is 4.
String used for Octave continuation lines.
Default is a backslash.
Non-nil means always display `inferior-octave-buffer' after sending a
command to the inferior Octave process.
Non-nil means always go to the next unsent line of Octave code after
sending a line to the inferior Octave process.
Non-nil means echo input sent to the inferior Octave process.
Turning on Octave mode runs the hook `octave-mode-hook'.
To begin using this mode for all `.m' files that you edit, add the
following lines to your init file:
(add-to-list 'auto-mode-alist '("\\.m\\'" . octave-mode))
To automatically turn on the abbrev and auto-fill features,
add the following lines to your init file as well:
To submit a problem report, enter M-x octave-submit-bug-report from an Octave mode buffer. This automatically sets up a mail buffer with version information already added. You just need to add a description of the problem, including a reproducible test case and send the message. (fn)