🚀 go-pugleaf

Brook --

Thanks for the reply; I'm sorry I didn't look hard enough to find it
in the FAQ.

At least for me, this is not fixed in 4.2.  The relevant code in
screen.c now says:

  size_hints.flags |= 
    (ugmask & (XValue|YValue)) ? USPosition : 
      (pgmask & (XValue|YValue)) ? PPosition : 
	0;

When I change it to

  size_hints.flags |= PPosition;

(which the FAQ suggests as the fix for 4.0p0) it behaves correctly.

When I run it with the original code under gdb:

ugmask = 15
pgmask = 12

(I have no idea what these are supposed to mean.)

XValue and YValue appear to be defined in Xutil.h as 1 and 2,
respectively, so the net result of this is to set size_hints.flags to
USPosition.

As I understand it, pgmask and ugmask are intended to be bit vectors
indicating which options the program and the user set, respectively.
I'm not quite sure where exactly the distinction is drawn, and
apparently the code is not too clear here either:  it does

  pgmask = XParseGeometry(xd.default_geometry,&x,&y,&dx,&dy);
  ugmask = XParseGeometry(xd.requested_geometry,&x,&y,&dx,&dy);

Where I find xd.default_geometry to be "80x24", the compiled-in
default, and xd.requested_geometry is "163x55+5+5", the value I put in
my .Xdefaults file.  So, my best guess is that what should really
happen is that if either the ugmask or the pgmask specifies an X/Y
pair, then in both cases size_hints.flags get or-ed with PPosition.
But I'm extremely willing to believe that the epoch developers know
better and will do the right thing, whatever it is.

Thanks!

Dave