casey@gauss.llnl.gov (Casey Leedom) (01/16/90)
In lines 2124 and 2125 in the R4 xterm/charproc.c:VTRealize() we see the lines: screen->max_col = (width - 1); /* units in character cells */ screen->max_row = (height - 1); /* units in character cells */ The corresponding lines (2052 and 2053) in the R4 xterm/charproc.c:VTRealize() we see the lines: screen->max_col = width; screen->max_row = height; I believe that this difference is responsible for xplaces reporting the wrong width and height geometry for xterms (off by one less than they should be). Is this a bug? A feature? What? I'm too stupid with regard to X to know the difference. Casey
casey@gauss.llnl.gov (Casey Leedom) (01/17/90)
I should also point out that this bug/feature seems to affect the sizes reported by xterm durring resize operations. When I'm resizing an xterm window to 80x30, its resizing window tells me that I've got 79x29 instead of 80x30. Somewhat surprisingly, when I ask the tty how large the window is via ``stty all'', the tty gives back 30 rows by 80 columns, so it's not off by one all through the code ...