[Octave-bug-tracker] [bug #53938] windows octave doesnt wait for to --eval statements to complete

[Mike Miller]

Follow-up Comment #1, bug #53938 (project octave):

I think everyone agrees that 'octave.exe --no-gui' should not be used. In
fact, I thought it was also generally agreed on that octave.exe should never
be used, that's why we have octave.bat and octave.vbs. And that's why the
'--no-gui' as an option runs octave-cli instead of octave-gui.

I would say on GNU and Unix systems there are three modes, 'octave-cli',
'octave --no-gui' (default), and 'octave --gui', but on Windows there are only
two modes that work. If we can make that easier somehow by adding options to
the bat file or deleting the octave.exe that users shouldn't be using, we
should do so.

IMHO calling 'octave --no-gui --no-window-system' should end up executing
'octave-cli' on all platforms.

Can we make octave.bat call 'octave-cli.exe' insetad of 'start octave-cli.exe'
as a first step?

What do you mean by calling octave-cli "doesnt get passed through the pkg
build system as a variable"? Meaning that the configure script still gets
called with OCTAVE=$fullpath/octave-4.4.0?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53938>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/