| Line 54... |
Line 54... |
| 54 |
\code{"console"} on Windows), or by letting \code{pager} be an \R
|
54 |
\code{"console"} on Windows), or by letting \code{pager} be an \R
|
| 55 |
function which will be called with arguments \code{(files, header,
|
55 |
function which will be called with arguments \code{(files, header,
|
| 56 |
title, delete.file)} corresponding to the first four arguments of
|
56 |
title, delete.file)} corresponding to the first four arguments of
|
| 57 |
\code{file.show} and take care of interfacing to the GUI.
|
57 |
\code{file.show} and take care of interfacing to the GUI.
|
| 58 |
|
58 |
|
| 59 |
The \command{R.app} GUI on OS X uses its internal pager irrespective
|
59 |
The \command{R.app} GUI on macOS uses its internal pager irrespective
|
| 60 |
of the setting of \code{pager}.
|
60 |
of the setting of \code{pager}.
|
| 61 |
|
61 |
|
| 62 |
Not all implementations will honour \code{delete.file}. In
|
62 |
Not all implementations will honour \code{delete.file}. In
|
| 63 |
particular, using an external pager on Windows does not, as there is
|
63 |
particular, using an external pager on Windows does not, as there is
|
| 64 |
no way to know when the external application has finished with the
|
64 |
no way to know when the external application has finished with the
|