[Blindmath] new command line processing of Octave 4.0.0

Godfrey, Jonathan A.J.Godfrey at massey.ac.nz
Sat Mar 12 10:02:13 UTC 2016


Hi all.

I found that the batch file approach I was trying needed to be altered from older versions of Octave to the new version 4.0.0.

In order of importance:

1.       The path to the m file must be specified, even if that means just saying it is in the current directory using .\ (see example below)

2.       I had to explicitly refer to the command line version to avoid an error being generated. That error message told me to reinstall Octave, which I had tried to no avail. I'm guessing there is a way to use switches instead of the explicit reference to the CLI version.

3.       Piping the results out to a text file is not as good as it used to be as the line breaks are not the correct Windows ones so formatting is lost. The m file must now explicitly state the diary file to send output to. That's probably better practice anyway.

4.       Octave now gets grumpy if an m file is named using a string that is an Octave command. My original file was called test.m which works, but throws a warning. Renaming to something unique helped.

The new command line I have is therefore:
"C:\Octave\Octave-4.0.0\bin\octave-cli" -q .\MyFile.m

I've just tested this on my Windows 7 64 bit laptop without errors. My selection of screen reader is irrelevant as there is no interaction between Octave and the screen when running in batch mode.

Btw: the solution was found via an email list's archive. I love email lists!!!

Cheers,
Jonathan





More information about the BlindMath mailing list