[Top][All Lists]

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

[Octave-bug-tracker] [bug #62863] Octave closes if empty editor tab is c

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #62863] Octave closes if empty editor tab is closed before .octaverc is finished
Date: Fri, 5 Aug 2022 08:52:29 -0400 (EDT)


                 Summary: Octave closes if empty editor tab is closed before
.octaverc is finished
                 Project: GNU Octave
               Submitter: philipnienhuis
               Submitted: Fri 05 Aug 2022 02:52:27 PM CEST
                Category: GUI
                Severity: 2 - Minor
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Microsoft Windows


Follow-up Comments:

Date: Fri 05 Aug 2022 02:52:27 PM CEST By: Philip Nienhuis <philipnienhuis>
(I've got used to this, has been happening for years and years, but OTOH it's
not as it should be. Not a showstopper, so severity -> minor.)

Steps to reproduce:
* create an .octaverc, only add the command 'pause (10)' in it
* fire up Octave GUI
* soon after GUI is up (but before 10 seconds are passed), click the close
button on the empty Editor tab.
==> result:
After .octaverc is finished (which can take the rest of the 10 secs.) Octave
vanishes from sight, w/o any trace or Windows popup. So I'm even not sure
whether Octave crashes or is just unexpectedly closing ... (I guess it's the

With regard to this the Octave GUI used to be more sensitive in the past;
resizing or closing panes, browsing in the file browser, loading other files
in the editor, etc sometimes gave the same behavior; but in 7.x.0 and 8.0.0 I
know only of closing the empty editor tab during startup.

My .octaverc takes quite a bit of time to get processed (a.o., loading several
packages I'm using daily) so I'm often tempted to start fiddling around in the
mean time: e.g., loading recent editor files, shifting panes around if the
layout got screwed up, etc., that's how I hit this.

AFAICS it started with Octave-6.1.0; the GUIs of yet older Octaves (I have
4.2.0 and 5.2.0 still around) are more robust w.r.t. this.


Reply to this item at:


Message sent via Savannah

reply via email to

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