Thu 29 Jun 2017 01:41:43 PM UTC, comment #4:
comment #3 is correct. the output is displayed as part of the buffer sent to the pager. (choosing an arbitrarily large output, I didn't think to scroll to the end and see if it was appended. it was). I guess I thought the pager output would only be restricted to the output of the command that triggered the pager, not the subsequent command, despite it all being executed in a single line.
TL;DR: as long as that's expected behavior, nothing to see here. report can be closed.
|
Thu 29 Jun 2017 07:02:05 AM UTC, comment #3:
I am not sure to understand correctly the sequence of commands to be issued, because in the second verbatim section it is not displayed. But: Isn't the concept "command echoed to the terminal" beside the point? With the pager on, echoing is done to the pager, and the pager decides what to show in the terminal. And in this case you didn't scroll down, so you did not see the echoing of 7+7. If you scroll down, isn't it there?
By the way: I see now that the pager output looks like this also at other peoples' installations. Since time immemorial (at least since 3.6.0, but I think actually 3.2.4, the first version I was using) I have had
PAGER_FLAGS(' ')
(note the space, because PAGER_FLAGS() won't accept an empty string) in my start-up file, because I find the behaviour customized by octave unusable. Otherwise, the scroll wheel does not affect the pager but scrolls the terminal, the pager terminates when I step through to the bottom and I then have to scroll the terminal to see the upper parts of the output, and in this case, but also when I end the pager with 'q', my terminal window becomes littered with graveyards of numbers, where in my opinion the major benefit of the pager is to collapse these outputs away. So I suggest to everyone to set the pager flags to empty and thus to use the vanilla behaviour of your pager, giving you a whole new (hopefully positive) experience of using octave, and perhaps the developers can comment about the reasons that these flags are there in the first place. By the way, I am using less as pager, but this is just what these flags are supposedly guided at giving the conditions for its execution in the system-wide start-up file.
|
Wed 28 Jun 2017 03:49:59 PM UTC, comment #2:
grumble. third time maybe? where's the Preview post button when you need it?
title may be a bit cryptic, but basically if given a series of commands, and an intermediate command results in calling the pager, the next command executes but is not echoed to the terminal.
Example:
no pager call
now with the pager
so it did the 7+7, but for some reason that was never echoed to the terminal. Agreed, this is an odd use case, but I don't think this is intentional.
|
Wed 28 Jun 2017 03:48:38 PM UTC, comment #1:
huh. looks fine in my email but all the verbatims are gone below. trying again:
title may be a bit cryptic, but basically if given a series of commands, and an intermediate command results in calling the pager, the next command executes but is not echoed to the terminal.
Example:
no pager call
|