GNOME Bugzilla – Bug 785827
Doesn't show lot of content by default
Last modified: 2018-05-22 13:06:34 UTC
Created attachment 356973 [details] gnome-logs vs gnome-system-log Using gnome-logs 3.24, the default size on the win/text/layout results in a low number of lines displayed and those being truncated which makes it difficult to read through a log. The attached screenshot shows the difference with gnome-system-log
Is https://git.gnome.org/browse/gnome-logs/commit/?id=8e9acf872ba7a5fc7c5bc360191a339ef14de178 (included in 3.25.1 and coming to stable in 3.26.0) enough?
Increasing the default window size is one thing we did to improve. Another feature Pranav worked on this summer is compressing similar events into one row. See commit 3bb233264c9de1a471db86344656ffa77ca9a1e4. He posted about it here[0]. *[0] https://pranavganorkar.wordpress.com/2017/06/24/gnome-logs-event-compression/
Those changes help indeed but the line still get truncated, what about allowing horizontal scrolling instead of truncating or decreasing the text size by 1?
(In reply to Sebastien Bacher from comment #3) > Those changes help indeed but the line still get truncated, what about > allowing horizontal scrolling instead of truncating or decreasing the text > size by 1? Emm. I don't think allowing horizontal scrolling is a good solution, and it might a bad one. One problem I can predict with it is that there might be conflict between scrolling down the whole list and scrolling left and right inside a single row. Currently Logs uses the same monospace font as the system. Simply decreasing the font size by 1 will break the consistency of the font used in the system, which I presume is not a good thing. In the screenshot you provide, gnome-system-log is maximized. So maximizing Logs should improve the experience more or less. And I agree there might be some improvement to be done at Logs side. Maybe the current layout is very good. To change it, I think some serious design work should be done.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-logs/issues/13.