[Top][All Lists]

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

[Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #55823] [octave forge] (io) xlsread(...) call using OCT interface interferes with GUI editor
Date: Mon, 11 Mar 2019 21:22:18 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.121 Safari/537.36

Update of bug #55823 (project octave):

                  Status:               Confirmed => Need Info              


Follow-up Comment #15:

Joel - OK, it sounds like this bug is still about something very specific to
the io package, that a script that has been saved and not modified is closed
in the editor. If that's what you're seeing, I think we need more information
about how to reproduce that. Can you verify that readtest.m is saved on disk,
no changes have been made to it, and you run it with what, F5 or F9? And then
the file is closed in the editor with no prompt shown?

I personally don't have Windows to test with, but I downloaded all the
attachments you provided in comment #2 and I don't see any problems on my
Debian system, the script stays open in the editor after multiple tries to run
it with either F5 or F9.

I will file a separate bug report about the script closing an unsaved file
when rmdir is called, that is very easy to reproduce.


Reply to this item at:


  Message sent via Savannah

reply via email to

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