Bug 133778

Summary: Data loss in xterm: screen content gets erased on font change
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Christian Steinruecken <christian.steinruecken>
Component: X11 ApplicationsAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED FIXED QA Contact: Stefan Dirsch <sndirsch>
Severity: Normal    
Priority: P5 - None CC: dickey
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Christian Steinruecken 2005-11-14 22:55:21 UTC
Xterm loses part of its screen content when it changes from a small to a bigger font: the lines get clipped to the visible area occupied by the previous window size in the smaller font.  This shouldn't happen... should it? The screen and scrollback buffer should be totally separate from the font size used. 
The clipped screen content is irreversibly lost,  and copy and paste will actually reproduce the clipped lines from then on.

Speculation as to what might cause this:
Could it be that xterm confuses resize and font change events in some unfortunate way?  E.g. when an xterm changes to a smaller font size, it calculates its new size, resizes the window, but catches the resize and calculates new buffer dimensions based on the old font size, thereby clipping the lines and losing the screen content?


Reproduction instructions:

Open an xterm, switch to a big font e.g. "Huge", create some screen output, e.g. with "ls -l", then switch to a small font e.g. "Tiny", and back to "Huge".
Comment 1 Thomas Dickey 2005-11-15 00:42:42 UTC
It shouldn't happen, but that's one of the bugs that I fixed
during 204/205 (and don't see with 206/207).  What does "xterm -v"
show?
Comment 2 Stefan Dirsch 2005-11-15 10:20:14 UTC
Since the bugreport is against SUSE 10.0, this is probably xterm-203. I can reproduce this problem with xterm-203 (10.0 xterm), but not with xterm-207, which will be on 10.1 Alpha3. Therefore I close this one as FIXED. Thanks for the feedback, Christian! Nice to hear from you. :-)