[Top][All Lists]

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

Re: Octave 5.2 io package

From: Philip Nienhuis
Subject: Re: Octave 5.2 io package
Date: Sat, 15 Feb 2020 20:41:42 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0

Hi Steph,

Please keep the mailing list in cc: or to:

The message is deliberately shown; there used to be, and in selected cases there still are, good reasons for emitting it. But admittedly these days the majority of users just use the built-in OCT interface which is fairly OK and fast for .xlsx, painfully slow for .ods, and simply never bother or don't know about e.g., Java-based spreadsheet I/O interfaces that may work (sometimes much) better for them.

Your point is taken; you're not the first one to bring this up either. I have some ideas on how to change it but ATM I'm working on getting io-2.6.0 released and due to other priorities I'm afraid I'll have to postpone this issue for a next release.



address@hidden wrote:
Thank you very much Philip.

<snip netiquette>

My routines read several Excel data files, my question is, can the message be 
suppressed? The message only show up once per session, you are correct. It just 
tells me something that I know already.

Thanks again for your time


-----Original Message-----
From: Help-octave <help-octave-bounces+steph=address@hidden> On Behalf Of 
Sent: Friday, 14 February 2020 23:24
To: address@hidden
Subject: Re: Octave 5.2 io package

steph wrote
I have successfully installed JAVA (64bit) and the IO package. When I
use IO in a .m script the output in the command window is "Detected
XLS interfaces:", any output produced by script follows this. Any
advice on how to suppress the "Detected XLS interfaces:"?

That message is supposed to show up just once per Octave session. The function 
that emits this message, xlsopen.m, scans for spreadsheet support I/O and 
stores found interfaces in persistent variables.

Based upon your description, one possibility is that your scripts contain a "clear 
-f" command somewhere; that's the most obvious way those persistent variables will 
be wiped.
Another possibility is that you open spreadsheet files with different 
interfaces each time. Can also happen if in one script a spreadsheet file is 
opened with a specifically requested interface, and in another script no 
interface is specified so xlsopen.m falls back to the default interface (OCT).

That's about all I can say here without further info from your side about what 
your scripts actually do with spreadsheet files.

BTW I decapitalized the subject line, we don't like shouting :-)


Sent from:

reply via email to

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