Bug 1255406 - Setting the environment variable PAGER=less makes the CLI unusable
Summary: Setting the environment variable PAGER=less makes the CLI unusable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine-cli
Classification: oVirt
Component: General
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-20 13:42 UTC by Juan Hernández
Modified: 2022-06-30 13:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 10:20:19 UTC
oVirt Team: Infra
Embargoed:
sbonazzo: ovirt-4.1-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46857 0 None None None 2022-06-30 13:05:54 UTC

Description Juan Hernández 2015-08-20 13:42:17 UTC
This issue was reported by Fabrice Bacchella in the users mailing lists. Quoting him:

ovirt shell uses PAGER for all output, even single line one. I was using PAGER=less, it made it barely usable. That's strange any way for a interactive shell.

Comment 1 Juan Hernández 2015-08-20 15:37:47 UTC
The reason for this is that by default the "less" program pauses after the output waiting for a key press from the user, regardless of the length of the output, and the CLI calls the "less" program for outputs with very small number of lines, some times even zero lines. For this reason the default pager command used by the CLI is "less -FXR", where the "-F" option tells "less" to not pause if the output doesn't take all the available screen space.

We should modify the CLI so that it uses the pager only for potentially large outputs and not when the number of lines is small (prompts, error messages, etc).

Meanwhile, as a workaround, you can set PAGER="less -F", that should help.

Comment 2 Juan Hernández 2016-05-10 10:20:19 UTC
There aren't plans to update the CLI, so this won't be fixed.


Note You need to log in before you can comment on or make changes to this bug.