[Octave-bug-tracker] [bug #44485] GUI: File | Exit from main menu doesn't work when Octave is busy

[Philip Nienhuis]

Follow-up Comment #22, bug #44485 (project octave):

Sorry that I may not be of much help as regards SIGABRT.
I do not know much about signal types on *nix; I can imagine Joe Average User
doesn't either.
Can you explain what use SIGABRT has for a plain user? If it has advantages,
I'd be all for it. But I just do not know.

While being a contributor with even push access, I'm less involved in lower
level stuff but much more interested in the ergonomical side: error catching,
meaningful actions if the unexpected (for users and developers) happens, that
sort of thing.
>From that POV I'm already quite content with your latest patch: IMO it does do
what a user would expect (apart from the backtrace dump on Linux).
As to that backtrace: I haven't tried Octave from a desktop shortcut, but
rather from the build dir with './run-octave &'. If users start the GUI from a
shortcut, the backtrace may not be an issue anyway, isn't it?


    _______________________________________________________

Reply to this item at:

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

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