File: Paging-Screen-Output.html

package info (click to toggle)
octave 6.2.0-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 124,192 kB
  • sloc: cpp: 322,665; ansic: 68,088; fortran: 20,980; objc: 8,121; sh: 7,719; yacc: 4,266; lex: 4,123; perl: 1,530; java: 1,366; awk: 1,257; makefile: 424; xml: 147
file content (183 lines) | stat: -rw-r--r-- 10,002 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Paging Screen Output (GNU Octave (version 6.2.0))</title>

<meta name="description" content="Paging Screen Output (GNU Octave (version 6.2.0))">
<meta name="keywords" content="Paging Screen Output (GNU Octave (version 6.2.0))">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<link href="index.html" rel="start" title="Top">
<link href="Concept-Index.html" rel="index" title="Concept Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Terminal-Output.html" rel="up" title="Terminal Output">
<link href="Terminal-Input.html" rel="next" title="Terminal Input">
<link href="Terminal-Output.html" rel="prev" title="Terminal Output">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
<link rel="stylesheet" type="text/css" href="octave.css">


</head>

<body lang="en">
<span id="Paging-Screen-Output"></span><div class="header">
<p>
Up: <a href="Terminal-Output.html" accesskey="u" rel="up">Terminal Output</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<span id="Paging-Screen-Output-1"></span><h4 class="subsubsection">14.1.1.1 Paging Screen Output</h4>

<p>When running interactively, Octave normally sends all output directly to the
Command Window.  However, when using the CLI version of Octave this can create
a problem because large volumes of data will stream by before you can read
them.  In such cases, it is better to use a paging program such as <code>less</code>
or <code>more</code> which displays just one screenful at a time.  With <code>less</code>
(and some versions of <code>more</code>) you can also scan forward and backward, and
search for specific items.  The pager is enabled by the command <code>more on</code>.
</p>
<p>Normally, no output is displayed by the pager until just before Octave is ready
to print the top level prompt, or read from the standard input (for example, by
using the <code>fscanf</code> or <code>scanf</code> functions).  This means that there may
be some delay before any output appears on your screen if you have asked Octave
to perform a significant amount of work with a single command statement.  The
function <code>fflush</code> may be used to force output to be sent to the pager (or
any other stream) immediately.
</p>
<p>You can select the program to run as the pager with the <code>PAGER</code> function,
and configure the pager itself with the <code>PAGER_FLAGS</code> function.
</p>
<span id="XREFmore"></span><dl>
<dt id="index-more">: <em></em> <strong>more</strong></dt>
<dt id="index-more-1">: <em></em> <strong>more</strong> <em>on</em></dt>
<dt id="index-more-2">: <em></em> <strong>more</strong> <em>off</em></dt>
<dd><p>Turn output pagination on or off.
</p>
<p>Without an argument, <code>more</code> toggles the current state.
</p>
<p>The current state can be determined via <code>page_screen_output</code>.
</p>
<p><strong>See also:</strong> <a href="#XREFpage_005fscreen_005foutput">page_screen_output</a>, <a href="#XREFpage_005foutput_005fimmediately">page_output_immediately</a>, <a href="#XREFPAGER">PAGER</a>, <a href="#XREFPAGER_005fFLAGS">PAGER_FLAGS</a>.
</p></dd></dl>


<span id="XREFPAGER"></span><dl>
<dt id="index-PAGER">: <em><var>val</var> =</em> <strong>PAGER</strong> <em>()</em></dt>
<dt id="index-PAGER-1">: <em><var>old_val</var> =</em> <strong>PAGER</strong> <em>(<var>new_val</var>)</em></dt>
<dt id="index-PAGER-2">: <em></em> <strong>PAGER</strong> <em>(<var>new_val</var>, &quot;local&quot;)</em></dt>
<dd><p>Query or set the internal variable that specifies the program to use
to display terminal output on your system.
</p>
<p>The default value is normally <code>&quot;less&quot;</code>, <code>&quot;more&quot;</code>, or
<code>&quot;pg&quot;</code>, depending on what programs are installed on your system.
See <a href="Installation.html">Installation</a>.
</p>
<p>When called from inside a function with the <code>&quot;local&quot;</code> option, the
variable is changed locally for the function and any subroutines it calls.
The original variable value is restored when exiting the function.
</p>
<p><strong>See also:</strong> <a href="#XREFPAGER_005fFLAGS">PAGER_FLAGS</a>, <a href="#XREFpage_005foutput_005fimmediately">page_output_immediately</a>, <a href="#XREFmore">more</a>, <a href="#XREFpage_005fscreen_005foutput">page_screen_output</a>.
</p></dd></dl>


<span id="XREFPAGER_005fFLAGS"></span><dl>
<dt id="index-PAGER_005fFLAGS">: <em><var>val</var> =</em> <strong>PAGER_FLAGS</strong> <em>()</em></dt>
<dt id="index-PAGER_005fFLAGS-1">: <em><var>old_val</var> =</em> <strong>PAGER_FLAGS</strong> <em>(<var>new_val</var>)</em></dt>
<dt id="index-PAGER_005fFLAGS-2">: <em></em> <strong>PAGER_FLAGS</strong> <em>(<var>new_val</var>, &quot;local&quot;)</em></dt>
<dd><p>Query or set the internal variable that specifies the options to pass
to the pager.
</p>
<p>When called from inside a function with the <code>&quot;local&quot;</code> option, the
variable is changed locally for the function and any subroutines it calls.
The original variable value is restored when exiting the function.
</p>
<p><strong>See also:</strong> <a href="#XREFPAGER">PAGER</a>, <a href="#XREFmore">more</a>, <a href="#XREFpage_005fscreen_005foutput">page_screen_output</a>, <a href="#XREFpage_005foutput_005fimmediately">page_output_immediately</a>.
</p></dd></dl>


<span id="XREFpage_005fscreen_005foutput"></span><dl>
<dt id="index-page_005fscreen_005foutput">: <em><var>val</var> =</em> <strong>page_screen_output</strong> <em>()</em></dt>
<dt id="index-page_005fscreen_005foutput-1">: <em><var>old_val</var> =</em> <strong>page_screen_output</strong> <em>(<var>new_val</var>)</em></dt>
<dt id="index-page_005fscreen_005foutput-2">: <em></em> <strong>page_screen_output</strong> <em>(<var>new_val</var>, &quot;local&quot;)</em></dt>
<dd><p>Query or set the internal variable that controls whether output intended
for the terminal window that is longer than one page is sent through a
pager.
</p>
<p>This allows you to view one screenful at a time.  Some pagers
(such as <code>less</code>&mdash;see <a href="Installation.html">Installation</a>) are also capable of moving
backward on the output.
</p>
<p>When called from inside a function with the <code>&quot;local&quot;</code> option, the
variable is changed locally for the function and any subroutines it calls.
The original variable value is restored when exiting the function.
</p>
<p><strong>See also:</strong> <a href="#XREFmore">more</a>, <a href="#XREFpage_005foutput_005fimmediately">page_output_immediately</a>, <a href="#XREFPAGER">PAGER</a>, <a href="#XREFPAGER_005fFLAGS">PAGER_FLAGS</a>.
</p></dd></dl>


<span id="XREFpage_005foutput_005fimmediately"></span><dl>
<dt id="index-page_005foutput_005fimmediately">: <em><var>val</var> =</em> <strong>page_output_immediately</strong> <em>()</em></dt>
<dt id="index-page_005foutput_005fimmediately-1">: <em><var>old_val</var> =</em> <strong>page_output_immediately</strong> <em>(<var>new_val</var>)</em></dt>
<dt id="index-page_005foutput_005fimmediately-2">: <em></em> <strong>page_output_immediately</strong> <em>(<var>new_val</var>, &quot;local&quot;)</em></dt>
<dd><p>Query or set the internal variable that controls whether Octave sends
output to the pager as soon as it is available.
</p>
<p>When the value is <code>false</code>, Octave buffers its output and waits until just
before the prompt is printed to flush it to the pager.  This is the default.
</p>
<p>When <code>page_screen_output</code> is <code>false</code>, this variable has no effect.
</p>
<p>When called from inside a function with the <code>&quot;local&quot;</code> option, the
variable is changed locally for the function and any subroutines it calls.
The original variable value is restored when exiting the function.
</p>
<p><strong>See also:</strong> <a href="#XREFpage_005fscreen_005foutput">page_screen_output</a>, <a href="#XREFmore">more</a>, <a href="#XREFPAGER">PAGER</a>, <a href="#XREFPAGER_005fFLAGS">PAGER_FLAGS</a>.
</p></dd></dl>


<span id="XREFfflush"></span><dl>
<dt id="index-fflush">: <em></em> <strong>fflush</strong> <em>(<var>fid</var>)</em></dt>
<dd><p>Flush output to file descriptor <var>fid</var>.
</p>
<p><code>fflush</code> returns 0 on success and an OS dependent error value
(-1 on Unix) on error.
</p>
<p>Programming Note: Flushing is useful for ensuring that all pending output
makes it to the screen before some other event occurs.  For example, it is
always a good idea to flush the standard output stream before calling
<code>input</code>.
</p>
<p><strong>See also:</strong> <a href="Opening-and-Closing-Files.html#XREFfopen">fopen</a>, <a href="Opening-and-Closing-Files.html#XREFfclose">fclose</a>.
</p></dd></dl>



<hr>
<div class="header">
<p>
Up: <a href="Terminal-Output.html" accesskey="u" rel="up">Terminal Output</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>