[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #31121] output of callback not directly printe
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #31121] output of callback not directly printed |
Date: |
Sat, 25 Sep 2010 21:06:58 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100819 Iceweasel/3.5.11 (like Firefox/3.5.11) |
Follow-up Comment #2, bug #31121 (project octave):
Output from disp goes through the pager, so this seems like normal behavior
to me. If I turn off the pager, I see the output immediately. But maybe the
rules for terminal output should be different if the output is coming from a
callback? Or we should flush pending output when events are processed? I
don't know, but both of those options seem complicated to me and could cause
some confusion if there is other output pending. Maybe it is better to just
turn off the pager if you want to see the output immediately?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31121>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/