ports/87424: xterm-205 stops showing window dimensions as character when the font size is changed

[Jukka A. Ukkonen]

>Number:         87424
>Category:       ports
>Synopsis:       xterm-205 stops showing window dimensions as character when the font size is changed
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 14 07:20:16 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Jukka A. Ukkonen
>Release:        4.11-STABLE
>Organization:
private citizen
>Environment:
FreeBSD mjolnir 4.11-STABLE FreeBSD 4.11-STABLE #0: Wed Sep 21 07:56:19 EET DST 2005     jau at mjolnir:/home/src/sys/compile/Mjolnir  i386

>Description:
              When xterm-205 is started it shows window dimensions as characters.
E.g. xterm-200 never stopped doing so.
Anyhow xterm-205 shows dimensions as characters when you change the window size
only as long as you do not touch the font size.
When one modifies the initial default font size to something else xterm-205 stops
showing the dimensions as characters and goes over to displaying pixel counts.
This is quite anoying for people who predominantly still read and write.

By the symptoms of it I would guess that someone has tried to optimize xterm code
by moving an apparently useless pixels per characters adjustment out of the event
loop (after a font change) to be done only when the program starts.
When xterm window scaling code no longer knows how large a character is it starts
displaying pixels only.

>How-To-Repeat:
              Follow these simple steps...
- Start xterm-205.
- Rescale the window and notice how the dimensions are still given as characters.
- Change the font size.
- Again rescale the window noticing how the dimensions suddenly appear as pixels.
- Try repeating the last 2 steps a few times to confirm what you just noticed.
- Be annoyed. ;-)

>Fix:
              Apparently a pixels per character size adjustment needs to be put
back somewhere after a font size change.
Details are still unknown.
Since xterm-200 and xterm-205 have been behaving differently in this respect,
a comparison of source code should give an idea what has been lost.

>Release-Note:
>Audit-Trail:
>Unformatted: