[Octave-bug-tracker] [bug #44751] Failure to exit when running Octave in --no-gui mode

[Dan Sebald]

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

When --no-gui is used, the link between Qt and Octave still exists.  So in
some sense the --no-gui and "with GUI" mode are similar.  --no-gui-libs is
different (no link established).

When there is a link established, Octave core "exit" will inquire with the
link (what would normally be the GUI) whether it is OK to shutdown.  That step
is typically used for closing/saving all editor windows and whatnot.

There needs to be a connection between this signal and some slot.  The latest
development version might also handle this by creating a main_window, but not
displaying.  There is a patch here:

https://savannah.gnu.org/bugs/?44116

that establishes that connection even in the case of main_window not
constructed.

Are you using the very latest development version?  Or something that might be
a week old or older?

For reference, there is also a patch in the works to address a related
problem, one of forcing a shutdown when Octave core appears busy:

https://savannah.gnu.org/bugs/?44485

but it's best to address that after the --no-gui issues are worked out.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/