[Bug: 21.5-b29] Initial frame geometry is unexpectedly narrow

Ben Wing ben at xemacs.org
Mon Mar 1 07:29:42 EST 2010


On Sat, Feb 27, 2010 at 5:26 AM, Stephen J. Turnbull
<turnbull at sk.tsukuba.ac.jp> wrote:
> Ben Wing writes:
>  > On Thu, Feb 25, 2010 at 12:41 PM, Stephen J. Turnbull
>  > <stephen at xemacs.org> wrote:
>
>  > > Since your frame changes (including the fix for the missing border bug
>  > > you committed earlier today), I'm getting a narrow frame.  I'm
>  > > guessing that XEmacs fails to update when I change the font in init.el
>  > > (see attached minimized init.el).  The result is in the attached image
>  > > narrow.png.
>  >
>  > Can you tell me when this started happening?  Did it just occur today
>  > or earlier?
>  >
>  > I.e. which changeset triggered it?
>
> It appears to be
>
> changeset:   5043:d0c14ea98592
> user:        Ben Wing <ben at xemacs.org>
> date:        Mon Feb 15 22:14:11 2010 -0600
> summary:     various frame-geometry fixes
>
> (Note that the revno 5043 may not correspond to your workspace.)
>
> I used bisect; for the sake of posterity, let me show how:
>
>    # Prepare the XEmacs part of the test.
>    cat >test.el <<EOT
>    (let (kill-emacs-hook)         ; may not be needed
>      (setup-fonts)                ; host-dependent, details on request
>      (kill-emacs (when (< (frame-width) 79)) 1))
>    EOT
>
>    # Prepare the test command for hg bisect.
>    cat >test.sh <<EOT
>    if make; then
>      src/xemacs -vanilla -l ./test.el
>    else
>      # The value 125 tells bisect to ignore the result
>      # and ignore this revision in the future.
>      exit 125
>    fi
>    EOT
>
>    # I don't know if this chmod is necessary,
>    # I did it before I corrected a different fatal bug in my script.
>    chmod a+x test.sh
>
>    # Just do it!
>    hg bisect -g 5042
>    hg bisect -b tip
>    hg bisect -c ./test.sh
>
> 5042 was good, as verified by "sh ./test.sh".  tip (5081) actually
> includes a couple of mq patches, which I didn't intend but clearly
> didn't hurt anything.  For the sake of posterity, here's the trace of
> bisect results:
>
>    Changeset 5064:501b5e84f5a7: bad
>    Changeset 5053:0e803dc6f096: skip
>    Changeset 5058:eb17f0c176ac: skip
>    Changeset 5052:92dc90c0bb40: skip
>    Changeset 5054:24372c7e0e8f: bad
>    Changeset 5047:07dcc7000bbf: skip
>    Changeset 5046:d4f666cda5e6: skip
>    Changeset 5048:32e1ae4c1e3a: skip
>    Changeset 5045:c3cc3fa503a2: bad
>    Changeset 5043:d0c14ea98592: bad
>
> Note that "skip" means that "make" failed.

Thanks!  I've never really used `hg bisect' before but I'll file this
away for next time I have to do a bisection.

Do you really get compile failures that often?  I do try to verify
that everything compiles before I commit.

ben



More information about the XEmacs-Beta mailing list