octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44445] Summary of failures in __run_test_suit


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #44445] Summary of failures in __run_test_suite__ of MXE-Octave 4.0.0.-rc1
Date: Fri, 06 Mar 2015 16:42:57 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30

Follow-up Comment #5, bug #44445 (project octave):

@comment #3:
Yep it is definitely https://savannah.gnu.org/bugs/?41699
Just:

test imread
exit

is enough.
OK, one issue (hmmm ...not solved, but...) identified.


Another thing:

While __run_test_suite__ is running in the GUI, selecting from the main menu
bar:
File | exit
does nothing until __run_test_suite__ is finished - Octave shuts down then.
Should we consider this a bug? i.e., should "File | Exit" have a higher
priority than anything running in Octave?


Similar goes to clicking the close button on the terminal pane. Is an octave
w/o terminal still a "complete" Octave? Should the terminal always be present
and visible?
FYI, in Matlab r2015a all panes have a "close" command on the right-click
menu, except for the terminal.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]