RE: address@hidden: RE: set-frame-position - is it a bug?]

[Drew Adams]

    If this cannot be reproduced with _any_ toolkit, then it is Windows
    specific (I see it on Windows with a build from 4 days ago).

    I don't know when I will be able to look into this; it sounds like an
    extremely marginal problem (who will need to ``resize the frame so
    that the menu-bar wraps''?).  Maybe someone will beat me to it.

I don't know whether you want to consider this "extremely marginal" - at
least two people reported it.

For a use case ("who will need to"): I have code that automatically resizes
each frame to fit its buffer contents. That code purposely ignores the menu
bar. The idea is to have as small a frame as possible, and still see all
buffer lines without wrapping or truncating. You don't want a wide,
half-empty frame with only narrow text in it, simply because the menu bar
happens to be wide for that mode.

The other user who reported this bug does not use automaic frame resizing
AFAIK. That user apparently resized the frame manually, or perhaps the
default frame size was itself too narrow for the menu bar in that particular
mode.

The point is that whether or not the menu bar is wrapped (regardless of how
that might come about), moving a frame should behave the same way (i.e.
behave normally).