Re: Some question on the interval package

[Rik]

On 06/16/2017 09:00 AM, address@hidden wrote:

Subject:

Re: Some questions on the interval package

From:

Joel Dahne <address@hidden>

Date:

06/16/2017 04:38 AM

To:

Oliver Heimlich <address@hidden>

CC:

"address@hidden" <address@hidden>, Octave Maintainers <address@hidden>

List-Post:

<mailto:address@hidden>

Content-Transfer-Encoding:

quoted-printable

Precedence:

list

MIME-Version:

1.0

References:

<address@hidden> <address@hidden>

In-Reply-To:

<address@hidden>

Message-ID:

<address@hidden>

Content-Type:

text/plain; charset="Windows-1252"

Message:

1

Revision 904 (size.m): You should change the texinfo macro @defmethod
into @deftypemethod and put the output arguments into curly braces.
Also you should format the new help text with @command{size} macros
(instead of plain quation marks).

I have done these changes. I will have to learn a bit more about texinfo
to understand what I'm doing though. Is it for 'make html' that the
texinfo is used? Because from what I can tell it is not visible in the
help text inside Octave.

Texinfo is used when creating HTML or PDF output.  In the Octave console the output format is plain text so the markup that you do is mostly unused, but it makes a big difference for the formats which do support markup.

disp.m: When printing an array with more than 2 dimensions I have
followed the normal Octave style. It looks like
 ans(:,:,1) =

   [0]   [0]
   [0]   [0]

Two small observations:

 1. The matrix label “ans(:,:,…)” should not be indented.
 2. Before the matrix label you need an additional blank line (not
before the first one). Remark: disp.m currently only supports “format
loose”, where there are blank lines between matrix labels and matrices.
Feel free to add support for “format compact”, but I don't know how to
properly detect the current display mode.

I have fixed the observations you made! Have not added support for
"format compact" though, I don't know how to properly detect this
either.

On the development branch, try 'help format'.  There is a calling form which returns both the format type and the format spacing

 -- [FORMAT, FORMATSPACING] = format

Check the second return argument to see whether it is "loose" or "compact".

--Rik