Mercurial > octave-nkf

changeset 2535:caa21ce81913

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[project @ 1996-11-19 19:53:55 by jwe]
author jwe
date Tue, 19 Nov 1996 19:53:57 +0000
parents c0770352f562
children 1d63e820ee13
files doc/interpreter/bugs.texi doc/interpreter/emacs.texi doc/interpreter/gnuinfo.texi doc/interpreter/gpl.texi doc/interpreter/install.texi doc/interpreter/invoke.texi doc/interpreter/io.texi doc/interpreter/linalg.texi doc/interpreter/plot.texi doc/interpreter/system.texi doc/interpreter/var.texi
diffstat 11 files changed, 119 insertions(+), 200 deletions(-) [+]
line wrap: on
line diff
--- a/doc/interpreter/bugs.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/bugs.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -57,13 +57,6 @@
 to turn the pager off.
 
 @item
-Control-C doesn't work properly in the pager on DEC Alpha systems
-running OSF/1 3.0.
-
-This appears to be a bug in the OSF/1 3.0 Bourne shell.  The problem
-doesn't appear on systems running OSF/1 1.3.
-
-@item
 If you get messages like
 
 @example
@@ -118,9 +111,6 @@
 Of course, this doesn't really fix the problem, but it does make it
 much less likely that you will run into trouble unless you are putting
 a very large number of lines on a given plot.
-
-@item
-String handling could use some work.
 @end itemize
 
 A list of ideas for future enhancements is distributed with Octave.  See
--- a/doc/interpreter/emacs.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/emacs.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -44,9 +44,9 @@
 
 @enumerate
 @item
-Make sure that the file @file{octave.el} (or even better, its
-byte-compiled version @file{octave.elc}) from the Octave distribution is
-somewhere in your load-path.
+Make sure that the file @file{octave.el} (or better, its byte-compiled
+version @file{octave.elc}) from the Octave distribution is somewhere in
+your load-path.
 
 @quotation
 @strong{Note:} The current version of @file{octave.el} was developed,
@@ -456,9 +456,9 @@
 
 You can also set up the Emacs Info reader for dealing with the results
 of Octave's @samp{help -i}.  For this, the package @file{gnuserv} needs
-to be installed, which unfortunately still does not come with GNU Emacs
-(it does with XEmacs).  It can be retrieved from any GNU Emacs Lisp Code
-Directory archive, e.g.@:
+to be installed.  The @file{gnuserv} package is not distributed with GNU
+Emacs, but it can be retrieved from any GNU Emacs Lisp Code Directory
+archive, e.g.@:
 @file{ftp://ftp.cis.ohio-state.edu/pub/gnu/emacs/elisp-archive},
 in the @file{packages} subdirectory.  There is also a newer version
 around (use archie to look for @file{gnuserv-2.1alpha.tar.gz}).
@@ -480,9 +480,9 @@
 that the Emacs variable @code{octave-help-files} is set correctly).  In
 this case, set @code{INFO_PROGRAM} to @code{"info-emacs-octave-help"}.
 
-If you use Octave from within Emacs, these settings are best done in the
-@file{~/.emacs_octave} startup file (or the file pointed to by the Emacs
-variable @code{inferior-octave-startup-file}).
+If you use Octave from within Emacs, it is probably best to put these
+settings in the @file{~/.emacs_octave} startup file (or in the file
+named by the Emacs variable @code{inferior-octave-startup-file}).
 
 @c Local Variables:
 @c TeX-command-default: "Texinfo"
--- a/doc/interpreter/gnuinfo.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/gnuinfo.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -568,20 +568,20 @@
 Here is a sample mode line for a window containing an uncompressed file
 named @file{dir}, showing the node @samp{Top}.
 
-@example
------Info: (dir)Top, 40 lines --Top---------------------------------------
+@smallexample
+-----Info: (dir)Top, 40 lines --Top------------------------------------
             ^^   ^   ^^^        ^^
           (file)Node #lines    where
-@end example
+@end smallexample
 
 When a node comes from a file which is compressed on disk, this is
 indicated in the mode line with two small @samp{z}'s.  In addition, if
 the info file containing the node has been split into subfiles, the name
 of the subfile containing the node appears in the modeline as well:
 
-@example
---zz-Info: (emacs)Top, 291 lines --Top-- Subfile: emacs-1.Z---------------
-@end example 
+@smallexample
+--zz-Info: (emacs)Top, 291 lines --Top-- Subfile: emacs-1.Z------------
+@end smallexample 
 
 When Info makes a node internally, such that there is no corresponding
 info file on disk, the name of the node is surrounded by asterisks
@@ -589,9 +589,9 @@
 are; the sample mode line below shows an internally constructed node
 showing possible completions:
 
-@example
------Info: *Completions*, 7 lines --All-----------------------------------
-@end example
+@smallexample
+-----Info: *Completions*, 7 lines --All--------------------------------
+@end smallexample
 
 @node Basic Windows, The Echo Area, The Mode Line, Window Commands
 @appendixsubsec Window Commands
--- a/doc/interpreter/gpl.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/gpl.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -356,7 +356,8 @@
 
 You should have received a copy of the GNU General Public License
 along with this program; if not, write to the Free Software
-Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA  02111-1307, USA.
+Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
+02111-1307, USA.
 @end smallexample
 
 Also add information on how to contact you by electronic and paper mail.
@@ -366,9 +367,10 @@
 
 @smallexample
 Gnomovision version 69, Copyright (C) 19@var{yy} @var{name of author}
-Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-This is free software, and you are welcome to redistribute it
-under certain conditions; type `show c' for details.
+Gnomovision comes with ABSOLUTELY NO WARRANTY; for details
+type `show w'.  This is free software, and you are welcome
+to redistribute it under certain conditions; type `show c'
+for details.
 @end smallexample
 
 The hypothetical commands @samp{show w} and @samp{show c} should show
--- a/doc/interpreter/install.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/install.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -18,8 +18,8 @@
 @itemize @bullet
 @item
 Run the shell script @file{configure}.  This will determine the features
-your system has (or doesn't have) and create a file named Makefile from
-each of the files named Makefile.in.
+your system has (or doesn't have) and create a file named
+@file{Makefile} from each of the files named @file{Makefile.in}.
 
 Here is a summary of the configure options that are most frequently used
 when building Octave:
@@ -48,15 +48,15 @@
 Print a summary of the options recognized by the configure script.
 @end table
 
-See the file INSTALL for more information about the command line options
-used by configure.  That file also contains instructions for compiling
-in a directory other than where the source is located.
+See the file @file{INSTALL} for more information about the command line
+options used by configure.  That file also contains instructions for
+compiling in a directory other than where the source is located.
 
 @item
 Run make.
 
 You will need a recent version of GNU make.  Modifying Octave's
-Makefiles to work with other make programs is probably not worth
+makefiles to work with other make programs is probably not worth
 your time.  We recommend you get and compile GNU make instead.
 
 For plotting, you will need to have gnuplot installed on your system.
@@ -66,17 +66,18 @@
 any but the most peripheral sense.
 
 For version @value{VERSION}, you must have the GNU C++ compiler (gcc)
-version 2.6.3 or later to compile Octave.  You will also need version
-2.6.1 of the GNU C++ class library (libg++).  If you plan to modify the
-parser you will also need GNU bison and fles.  If you modify the
-documentation, you will need GNU Texinfo, along with the patch for the
-makeinfo program that is distributed with Octave.
+version 2.7.2 or later to compile Octave.  You will also need version
+2.7.1 or 2.7.2 of the GNU C++ class library (libg++).  If you plan to
+modify the parser you will also need GNU bison and fles.  If you modify
+the documentation, you will need GNU Texinfo, along with the patch for
+the makeinfo program that is distributed with Octave.
 
 GNU make, gcc, and libg++, gnuplot, bison, flex, and Texinfo are all
 available from many anonymous ftp archives.  The primary site is
 prep.ai.mit.edu, but it is often very busy.  A list of sites that mirror
 the software on prep is available by anonymous ftp from prep.ai.mit.edu
-in the file /pub/gnu/GNUinfo/FTP, or by fingering fsf@@prep.ai.mit.edu.
+in the file @file{/pub/gnu/GNUinfo/FTP}, or by fingering
+fsf@@prep.ai.mit.edu.
 
 If you don't have a Fortran compiler, or if your Fortran compiler
 doesn't work like the traditional Unix f77, you will need to have the
@@ -169,11 +170,6 @@
 
 @itemize @bullet
 @item
-If @code{configure} fails when trying to create its output files, you
-may have found a limitation in the version of @code{sed} on your
-system.  Using GNU @code{sed} avoids the problem.
-
-@item
 On some SCO systems, @code{info} fails to compile if
 @code{HAVE_TERMIOS_H} is defined int @file{config.h}.  Simply removing
 the definition from @file{info/config.h} should allow it to compile.
@@ -222,43 +218,24 @@
 with Octave.  See the file MAKEINFO.PATCH for more details.
 
 @item
-If you don't have NPSOL but you still want to be able to solve NLPs, or
-if you don't have QPSOL but you still want to solve QPs, you'll need to
-find replacements or order them from Stanford.  If you know of a freely
-redistributable replacement, please let us know---we might be interested
-in distributing it with Octave.
-
-You can get more information about NPSOL and QPSOL from
-
-@quotation
-Stanford Business Sofrtware, Inc.@*
-2680 Bayshore Parkway, Suite 304@*
-Mountain View, CA 94043@*
-Tel: (415) 962-8719@*
-Fax: (415) 962-1869
-@end quotation
-
-Octave may soon support FSQP, an NLP solver from Andre Tits
-(andre@@src.umd.edu) of the University of Maryland.  FSQP is available
-free of charge to academic sites, but can not be redistributed to third
-parties.
-
-@item
 Some of the Fortran subroutines may fail to compile with older versions
 of the Sun Fortran compiler.  If you get errors like
 
-@example
+@smallexample
 zgemm.f:
 	zgemm:
 warning: unexpected parent of complex expression subtree
-zgemm.f, line 245: warning: unexpected parent of complex expression subtree
+zgemm.f, line 245: warning: unexpected parent of complex
+  expression subtree
 warning: unexpected parent of complex expression subtree
-zgemm.f, line 304: warning: unexpected parent of complex expression subtree
+zgemm.f, line 304: warning: unexpected parent of complex
+  expression subtree
 warning: unexpected parent of complex expression subtree
-zgemm.f, line 327: warning: unexpected parent of complex expression subtree
+zgemm.f, line 327: warning: unexpected parent of complex
+  expression subtree
 pcc_binval: missing IR_CONV in complex op
 make[2]: *** [zgemm.o] Error 1
-@end example
+@end smallexample
 
 @noindent
 when compiling the Fortran subroutines in the @file{libcruft}
@@ -307,31 +284,19 @@
 .objc_class_name_NXBundle
 @end example
 
-One kludge around this problem is to extract @file{termios.o} from
+One kluge around this problem is to extract @file{termios.o} from
 @file{libposix.a}, put it in Octave's @file{src} directory, and add it
-to the list of files to link together in the Makefile.  Suggestions for
+to the list of files to link together in the makefile.  Suggestions for
 better ways to solve this problem are welcome!
 
 @item
-With g++ 2.6.3 (and possibly other 2.6.x versions) on some Intel x86
-systems, compiling @file{Array-d.cc} fails with the messages like
-
-@example
-as: /tmp/cc005254.s:4057: Local symbol LBB103 never defined.
-as: /tmp/cc005254.s:4057: Local symbol LBE103 never defined.
-@end example
-
-@noindent
-A possible workaround for this is to compile without @code{-g}.
-
-@item
 If Octave crashes immediately with a floating point exception, it is
 likely that it is failing to initialize the IEEE floating point values
 for infinity and NaN.
 
 If your system actually does support IEEE arithmetic, you should be able
 to fix this problem by modifying the function @code{octave_ieee_init} in
-the file @file{sysdep.cc} to correctly initialize Octave's internal
+the file @file{lo-ieee.cc} to correctly initialize Octave's internal
 infinity and NaN variables.
 
 If your system does not support IEEE arithmetic but Octave's configure
@@ -344,72 +309,26 @@
 proper thing to do.
 
 @item
-Using the -O flag with old versions of the Sun Fortran compiler
-apparently prevents if from compiling some of the Fortran subroutines
-that Octave uses.  The workaround is to not use -O for those
-subroutines.
-
-@ignore
-@c These next two items should no longer be problems, since g++ and
-@c libg++ use a different method for installing an appropriate set of
-@c header files.
-@item
-Problems with finite and isinf on systems that don't have @code{isinf()}
-but do have @code{finite()}.
+If you don't have NPSOL but you still want to be able to solve NLPs, or
+if you don't have QPSOL but you still want to solve QPs, you'll need to
+find replacements or order them from Stanford.  If you know of a freely
+redistributable replacement, please let us know---we might be interested
+in distributing it with Octave.
 
-The copy of @file{math.h} supplied with libg++ version 2.3 (and possibly
-other versions as well) declares @code{finite()} as
-
-@example
-double finite (double);
-@end example
-
-@noindent
-even though some (many? all?) systems declare it as
-
-@example
-int finite (double);
-@end example
-
-If the copy of @file{math.h} from libg++ was installed, you should edit
-it so that the libg++ declaration of @samp{finite()} matches the
-system's.
+You can get more information about NPSOL and QPSOL from
 
-@item
-Problems compiling octave.cc on RS/6000 (and possibly other)
-systems:
-
-If octave.cc fails to compile due to parse errors in system include
-files and undeclared subroutines like `gethostname' and `endpwent',
-it is probably because not all of the libg++ include files have been
-installed.  This appears to be a problem with libg++ version 2.3.
-Here's a fix:
-
-Apply the following patch to @file{libg++/config/rs6000.mh} and re-run
-make install for libg++.
+@quotation
+Stanford Business Sofrtware, Inc.@*
+2680 Bayshore Parkway, Suite 304@*
+Mountain View, CA 94043@*
+Tel: (415) 962-8719@*
+Fax: (415) 962-1869
+@end quotation
 
-@example
-*** rs6000.mh~  Mon Aug 17 19:18:44 1992
---- rs6000.mh   Mon Dec 28 23:54:57 1992
-***************
-*** 3,6 ****
-  # /usr/include/unistd.h has write(int, char*, unsigned) instead
-  # of write(int, const void*, size_t).  This causes problems due
-  # to g++ new pedantic dis-allowal of void* -> char* conversions.
-! G_CONFIG_ARGS = "HAVE_UNISTD=0 /*broken*/"
---- 3,12 ----
-  # /usr/include/unistd.h has write(int, char*, unsigned) instead
-  # of write(int, const void*, size_t).  This causes problems due
-  # to g++ new pedantic dis-allowal of void* -> char* conversions.
-! G_CONFIG_ARGS = "HAVE_UNISTD=0 /*broken*/"
-! 
-! # If the C include files are C++-ready (with extern "C"),
-! # define: HAVE_CPLUS_EXTERN = 1 and: WRAP_C_INCLUDES =
-! # If not, define HAVE_CPLUS_EXTERN = 0, and do not define
-! # WRAP_C_INCLUDES here.
-! HAVE_CPLUS_EXTERN = 0
-@end example
-@end ignore
+Octave may soon support FSQP, an NLP solver from Andre Tits
+(andre@@src.umd.edu) of the University of Maryland.  FSQP is available
+free of charge to academic sites, but can not be redistributed to third
+parties.
 @end itemize
 
 @node Binary Distributions,  , Installation Problems, Installation
@@ -458,10 +377,8 @@
 @item lib/octave/@var{version}/exec/@var{host_type}
 Executables to be run by Octave rather than the user.
 
-@ignore
 @item lib/octave/@var{version}/oct/@var{host_type}
 Object files that will be dynamically loaded.
-@end ignore
 
 @item lib/octave/@var{version}/imagelib
 Image files that are distributed with Octave.
@@ -485,7 +402,8 @@
 @end example
 
 @noindent
-Octave will then be installed in subdirectories of the directory @file{/some/other/directory}
+will install Octave in subdirectories of the directory
+@file{/some/other/directory}.
 @end itemize
 
 @node Creating a Binary Distribution,  , Installing Octave from a Binary Distribution, Binary Distributions
@@ -495,9 +413,9 @@
 
 @itemize @bullet
 @item
-Build Octave in the same directory as the source.  This is required
-since the @samp{binary-dist} targets in the Makefiles will not work if
-you compile outside the source tree.
+You must build Octave in the same directory as the source.  This is
+required since the @samp{binary-dist} targets in the makefiles will not
+work if you compile outside the source tree.
 
 @item
 Use @samp{CFLAGS=-O CXXFLAGS=-O LDFLAGS=} as arguments for Make because
--- a/doc/interpreter/invoke.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/invoke.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -189,14 +189,15 @@
 
 @defvr {Built-in Variable} program_invocation_name
 @defvrx {Built-in Variable} program_name
-When Octave starts, the value of @code{program_invocation_name} is
-automatically set to the name that was typed at the shell prompt to run
-Octave, and the value of @code{program_name} is automatically set to the
-final component of @code{program_invocation_name}.  For example, if you
-typed @file{@value{OCTAVEHOME}/bin/octave} to start Octave,
+When Octave starts, the value of the built-in variable
+@code{program_invocation_name} is automatically set to the name that was
+typed at the shell prompt to run Octave, and the value of
+@code{program_name} is automatically set to the final component of
+@code{program_invocation_name}.  For example, if you typed
+@file{@value{OCTAVEHOME}/bin/octave} to start Octave,
 @code{program_invocation_name} would have the value
-@file{@value{OCTAVEHOME}/bin/octave}, and @code{program_name} would have the
-value @code{octave}.
+@file{@value{OCTAVEHOME}/bin/octave}, and @code{program_name} would have
+the value @code{octave}.
 
 If executing a script from the command line (e.g., @code{octave foo.m}
 or using an executable Octave script, the program name is set to the
--- a/doc/interpreter/io.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/io.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -665,10 +665,10 @@
 Conversions}, for details.
 
 @item @samp{%g}, @samp{%G}
-Print a floating-point number in either normal or exponential notation,
-whichever is more appropriate for its magnitude.  @samp{%g} uses
-lower-case letters and @samp{%G} uses upper-case.  @xref{Floating-Point
-Conversions}, for details.
+Print a floating-point number in either normal (fixed-point) or
+exponential notation, whichever is more appropriate for its magnitude.
+@samp{%g} uses lower-case letters and @samp{%G} uses upper-case.
+@xref{Floating-Point Conversions}, for details.
 
 @item @samp{%c}
 Print a single character.  @xref{Other Output Conversions}.
--- a/doc/interpreter/linalg.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/linalg.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -657,10 +657,8 @@
 @ifinfo
 Pade'
 @end ifinfo
-approximation method with
-three step preconditioning (SIAM Journal on Numerical Analysis, 1977).
-
-Diagonal
+approximation method with three step preconditioning (SIAM Journal on
+Numerical Analysis, 1977).  Diagonal
 @iftex
 @tex
 Pad\'e
--- a/doc/interpreter/plot.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/plot.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -80,7 +80,8 @@
 the command
 
 @example
-gplot [-11:11] [-1.1:1.1] data with lines, data using 1:3 with impulses
+gplot [-11:11] [-1.1:1.1] \
+  data with lines, data using 1:3 with impulses
 @end example
 
 @noindent
--- a/doc/interpreter/system.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/system.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -492,13 +492,19 @@
 argument @code{--exec-path PATH}, or by setting the value of
 @code{EXEC_PATH} in a startup script.  If the value of @code{EXEC_PATH}
 begins (ends) with a colon, the directories
-@code{OCTAVE_HOME/libexec/octave/site/exec/ARCH},
-@code{OCTAVE_HOME/libexec/octave/VERSION/exec/ARCH} and
-@code{OCTAVE_HOME/bin} are prepended (appended) to @code{EXEC_PATH},
-where @code{OCTAVE_HOME} is the top-level directory where all of Octave
-is installed (@file{/usr/local} by default).  If you don't specify a
-value for @code{EXEC_PATH} explicitly, these special directories are
-prepended to your shell path.
+
+@example
+OCTAVE_HOME/libexec/octave/site/exec/ARCH
+OCTAVE_HOME/libexec/octave/VERSION/exec/ARCH
+OCTAVE_HOME/bin
+@end example
+
+@noindent
+are prepended (appended) to @code{EXEC_PATH}, where @code{OCTAVE_HOME}
+is the top-level directory where all of Octave is installed
+(@file{/usr/local} by default).  If you don't specify a value for
+@code{EXEC_PATH} explicitly, these special directories are prepended to
+your shell path.
 @end defvr
 
 @deftypefn {Built-in Function} {} getenv (@var{var})
--- a/doc/interpreter/var.texi	Tue Nov 19 19:06:30 1996 +0000
+++ b/doc/interpreter/var.texi	Tue Nov 19 19:53:57 1996 +0000
@@ -180,16 +180,17 @@
 @code{alpha-dec-osf3.2}).
 
 @smallexample
-EDITOR                        "vi"
-EXEC_PATH                     ":$PATH"
-INFO_FILE                     "OCT_HOME/info/octave.info"
-INFO_PROGRAM                  "OCT_HOME/libexec/octave/VERSION/exec/SYS/info"
-LOADPATH                      ".:OCT_HOME/lib/VERSION"
-PAGER                         "less", or "more"
-PS1                           "\s:\#> "
-PS2                           "> "
-PS4                           "+ "
-automatic_replot              0
+EDITOR                  "vi"
+EXEC_PATH               ":$PATH"
+INFO_FILE               "OCT_HOME/info/octave.info"
+INFO_PROGRAM            "OCT_HOME/libexec/octave/VERSION/exec/SYS/info"
+LOADPATH                ".:OCT_HOME/lib/VERSION"
+PAGER                   "less", or "more"
+PS1                     "\s:\#> "
+PS2                     "> "
+PS4                     "+ "
+automatic_replot        0
+
 beep_on_error                 0
 completion_append_char        " "
 default_return_value          []
@@ -200,6 +201,7 @@
 history_file                  "~/.octave_hist"
 history_size                  1024
 ignore_function_time_stamp    "system"
+
 implicit_str_to_num_ok        0
 ok_to_lose_imaginary_part     "warn"
 output_max_field_width        10
@@ -209,8 +211,8 @@
 prefer_zero_one_indexing      0
 print_answer_id_name          1
 print_empty_dimensions        1
-@c read_only_constants           1
 resize_on_range_error         1
+
 return_last_computed_value    0
 save_precision                17
 saving_history                1
@@ -221,6 +223,7 @@
 treat_neg_dim_as_zero         0
 warn_assign_as_truth_value    1
 warn_comma_in_global_decl     1
+
 warn_divide_by_zero           1
 warn_function_name_clash      1
 whitespace_in_literal_matrix  ""
@@ -230,13 +233,13 @@
 line option.
 
 @smallexample
-Variable        Environment Variable        Option 
---------        --------------------        ------
+Variable        Environment Variable    Option 
+--------        --------------------    ------
 EDITOR          EDITOR
-EXEC_PATH       OCTAVE_EXEC_PATH            --exec-path PATH    
-LOADPATH        OCTAVE_PATH                 --path PATH
-INFO_FILE       OCTAVE_INFO_FILE            --info-file FILE
-INFO_PROGRAM    OCTAVE_INFO_PROGRAM         --info-program PROGRAM
+EXEC_PATH       OCTAVE_EXEC_PATH        --exec-path PATH    
+LOADPATH        OCTAVE_PATH             --path PATH
+INFO_FILE       OCTAVE_INFO_FILE        --info-file FILE
+INFO_PROGRAM    OCTAVE_INFO_PROGRAM     --info-program PROGRAM
 history_size    OCTAVE_HISTSIZE
 history_file    OCTAVE_HISTFILE
 @end smallexample