Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output to be available for display in its whole width #32

Closed
Ricky-Tigg opened this issue Nov 11, 2019 · 4 comments
Closed

Output to be available for display in its whole width #32

Ricky-Tigg opened this issue Nov 11, 2019 · 4 comments

Comments

@Ricky-Tigg
Copy link

OS: Fedora; Component: less.x86_64 551-2.fc31 @anaconda

Entrancement requestoutput to be available for display. in its whole width.

Command involved lsblk -O | less. Tested under a 15.60-inched display, under Gnome standard v.3.34.1 on Wayland, under gnome-terminal.x86_64 3.34.2 Snapshots took while terminal window was in full screen mode, which is equivalent to

$ stty size
45 158

Default output displayed, which is according to vertical axis.

command_output_lsblk_-O_1

Output displayed according to horizontal axis –by invoking right-arrow key–. The beginning of the ouput is not available for displaying; here for instance the content listed in the NAME column.

command_output_lsblk_-O_2

@gwsw
Copy link
Owner

gwsw commented Nov 11, 2019

I'm sorry, I don't quite understand this. Obviously if the screen is 158 columns wide and the text is wider than that, then the whole line can't be displayed without wrapping, which your first screenshot shows. This screenshot also shows that the entire text is being displayed. When you press right-arrow you are asking to see something different -- what exactly do you expect to see after you press right-arrow?

@Ricky-Tigg
Copy link
Author

Ricky-Tigg commented Nov 12, 2019

Hey. A whole line of the output not be displayed without wrapping; That presently was as a requirement in order to reproduce present issue, not an issue by itself. As well size values supplied by me, they were there only to show under what circumstance on my system that requirement was met, thus those values neither were meant to be an issue. At last, even if a test would be conducted by relying on an endless-sized screen, gnome-terminal would display outputs according to its internal restrictions, which columns x rows respective values are 511 x 511.

Relevance of first snapshot presence came from that it contained the beginning of the output; it had to be there for a unique purpose; to confirm that the object of issue was pertinent. Here is what we knew we could expect; a view whose beginning would have matched output resulting from lsblk -o name while switching from default view to a view according to horizontal axis..

output|lsblk_-o_name_2

Further testing brought a new negative element that grows severity of depicted issue. Along with each click onto left-arrow and right-arrow keys, the tool does not display a new segment of the whole output.

Here is an illustration of the next segment, –invoked by right-arrow– while previous segment was the one illustrated in second snapshot:

output|lsblk_-o_name_1

@gwsw
Copy link
Owner

gwsw commented Nov 18, 2019

I'm sorry, I still cannot understand what you are asking for. The --shift option specifies how many characters the output is shifted when you press the right-arrow or left-arrow key. Does that help your issue? If not, perhaps you could construct a screenshot of how you would like the output to appear after you press the arrow key, rather than trying to explain it in words.

@Ricky-Tigg
Copy link
Author

You should probably have by now understood that those commands should had be run in a terminal emulator and they required few knowledge if not at al,lin order to interpret correctly their outputs.. Undoubtedly you would have had few difficulties whit those outputs; I won't guess where, why, and how you all alone managed to achieve that state.

No doubt you shall keep on acting that way as you would not even know something related to the behaviour of the tool you seem to be maintainer, keeping on pretending not to understand a mysterious unknown, which is to indicate you did not indeed understand that a behaviour supported by evidences is wrong when it does fail in its task –to produce visually all parts of an output, as you had perfectly understood.

@gwsw gwsw closed this as completed Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants