GNOME Bugzilla – Bug 395638
font size reduction in a maximized terminal is done poorly
Last modified: 2014-04-27 08:46:39 UTC
Problem: Upon reduction of font size in a maximized terminal, the top left corner is used as an origin for resizing. The terminal contents are shifted into the top left of the terminal which now has a larger height and width. The terminal contents are not re-distributed to take advantage of the new width where line wraps had previously occurred. Suggestion: Use the leftmost character of the lowest line as a fixed point that will be anchored to the bottom left of the terminal during font size reduction. Allow higher lines to be re-wrapped to utilize the greater width. Fill in space above those lines that were visible in the smaller terminal with scrollback buffer contents if possible. Steps to reproduce: 1)Open a gnome-terminal 2)Maximize the terminal 3)Use ctrl+ to increase the font size 4)execute a command that outputs more lines than are currently displayed 5)Use ctrl- to decrease the font size
The rewrapping is bug 336238. The fixed-point when resizing is top-left only if the scrollbar is not at the bottom extreme. That is, if scroll is not following output. I agree that top is not the best fixed-point, but I also don't think that bottom is. Middle makes the most sense to me for a terminal widget, but that is too unsimilar to other text widgets. So, I'm inclined to close this as WONTFIX.
We are voting about a more general question at http://brainstorm.ubuntu.com/idea/20553/
Hi Behdad, I once reported something along those lines in https://bugzilla.redhat.com/show_bug.cgi?id=696299 One of the manifestations of that bug can be seen as http://jeff.ecchi.ca/public/gnome-terminal-395638-and-336238.webm Is that the same or that's bug #696299 or something else entirely?
It's hard to say. It may be a terminal or a bash bug, or the interaction of the two... Rule of thumb is, if it works in xterm, then file it separately here and we'll fix. At any rate, please don't comment on closed reports. File new bugs, even if you're not sure whether it's the same.
I tested with xterm and saw the same problem as what's in my screencast. > At any rate, please don't comment on closed reports. > File new bugs, even if you're not sure whether it's the same. Right, but this bug report is still open, actually :) The thing is, I'm not really sure what triggers the bug or how to describe it, other than what's shown in the screencast...
WONTFIX as per comment 2.