[Top][All Lists]

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

Re: Program still does not print out while running

From: Robert A. Macy
Subject: Re: Program still does not print out while running
Date: Fri, 29 Apr 2005 08:48:43 -0700


That's it!  

Somewhere, page_screen_output gets set to 1 during the

I don't request it, so no idea where it comes from.  but
after placing the line to set this variable to 0 in the
script, the script prints out properly.  

So my workaround is simply to keep the variable set to zero
and all is well.  

Regarding upgrade...

I have XP, just don't like to use it - too slow
Is there a new binary for Windows that just installs?

                - Robert -

On Fri, 29 Apr 2005 11:13:33 -0400
 "John W. Eaton" <address@hidden> wrote:
> On 29-Apr-2005, Robert A. Macy wrote:
> | The script says...
> | page_output_immediately=1;
> | ...but fails to print out until the end
> | 
> | my emails incorrectly said...
> | page_out_immediately=1;
> | sorry.
> | 
> | Reading the 
> | >> help page_output_immediately
> | says that the default is zero, so this program should
> never
> | have been printing out when I first start up octave,
> yet
> | that's the only time the script prints out while
> running.
> | hmmmm....
> I don't understand what you mean here, but if you really
> want to
> bypass the pager, use page_screen_output = 0 (also
> equivalent to
> more ("off")).
> Maybe you have found a bug.  But I think
> page_output_immediately works
> for me, so perhaps it has been fixed.  You said you are
> using 2.1.50
> on Windows 98.  At some point, you might consider
> upgrading to a newer
> version of Octave (if not a newer OS).  Octave 2.1.50 is
> almost two
> years old now, and a lot has changed in those two years.
> If you think you have found a bug in Octave, then please
> submit a
> complete report that someone can use to reproduce the
> problem.
> Otherwise, we have nothing to debug.  But first, it would
> be helpful
> if you could verify whether the problem has been fixed in
> the current
> recommended version of Octave.
> The longer you keep using very old versions of Octave,
> the more likely
> it is that you will hit bugs that have already been
> fixed, so sending
> reports for those problems without first checking to see
> whether they
> have been fixed in the current recommended version tends
> to waste the
> time of the people who can help.
> jwe

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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