address@hidden: RE: ibuffer problem with pop-up-frames non-nil]

[Richard M. Stallman]

Can anyone reproduce this?

------- Start of forwarded message -------
From: "Drew Adams" <address@hidden>
To: <address@hidden>
Date: Mon, 7 Nov 2005 14:34:19 -0800
In-reply-to: <address@hidden>
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
Subject: RE: ibuffer problem with pop-up-frames non-nil
Sender: address@hidden
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python
X-Spam-Level: 
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63

BTW, I forgot one other invisible-frame bug (AFAICT):


    -----Original Message-----
    Sent: Tuesday, January 18, 2005 8:35 AM
    To: Emacs-Devel
    Subject: multiple frames with same name on (frame-list) - what is the
    cause?

    I didn't get any reply on this from help-gnu-emacs. I'm hoping
    that someone
    here might have some insight on it. Thanks - Drew

    ----

    As far as I know, I am not creating any multiple frames with
    the same name.
    After a sequence of operations such as `iconify-frame',
    `make-frame-invisible', and `make-frame-visible', however, I
    somehow end up
    with some frames listed multiple times in `(frame-list)'.  I'm
    not sure of
    the exact sequence of such operations that leads to the problem.

    Actually, the "duplicate" frames have the same name, but they
    are different
    frames, as indicated by their hex ids. One of them will have
    frame-parameter
    `(visible . t)', and the others will have frame-parameter `(visible)'.
    Again, all of these frames are listed in `(frame-list)'.

    These multiple frames are messing things up when I try, for instance, to
    iterate over `(frame-list)'.

    Anyone have an idea where the multiple frames on `(frame-list)'
    are coming
    from? I don't see anything in the various function definitions
    or the doc
    that would indicate that one of the functions (e.g.
    `make-frame-visible' or
    `make-frame-invisible') would create a new frame instead of
    operating on an
    existing frame (its argument).

    BTW, the only way that I'm using `make-frame-visible' is through
    `frame-configuration-to-register' followed by
    `jump-to-register', and these
    functions use `current-frame-configuration', which just iterates over
    `(frame-list)'.

    I see this problem in both Emacs 20.7 and Emacs 21.3.50 (from CVS July
    2004).

    Thanks,

      Drew



_______________________________________________
Emacs-pretest-bug mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------