[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: Tue, 12 Mar 2019 14:53:56 -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

Follow-up Comment #21, bug #55823 (project octave):

@philip When I read the original bug here, I don't see anything about an
unsaved tab in the editor. Joel gave a script file 'readtest.m' and said that
running it in the editor triggered this bug. He said that the file was closed
in the editor and then he reopened it, implying that the file was indeed
already saved.

Are you saying that you are unable to reproduce this bug with the files that
Joel provided in comment #2? If so then this bug needs more information from
Joel about precisely how to reproduce this. If it can't be reproduced except
by pasting into a new unsaved tab, then this should be closed and bug #55888
will continue.

I asked Joel in comment #15 for more details, for example how exactly was the
script run in the editor, was it saved or unsaved, was it run with F5 or F9,


Reply to this item at:


  Message sent via Savannah

reply via email to

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