bug#6786: 23.2; Ido-mode switch-to-buffer switches frames

[Joel James Adamson <adamsonj@email.unc.edu>]

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

martin rudalics <rudalics@gmx.at> writes:

>> emacs -Q; open a new frame using "C-x 5 2" and switch to that frame.
>> Then switch from *scratch* to *Messages* in the first frame.  Enable
>> ido-mode using "M-x ido-mode".  Switch to the second frame and try
>> switching to *Messages*.  The point (and focus) move to the other
>> window.
>>
>> Setting the ido-mode variables `ido-default-file-method' and
>> `ido-default-buffer-method' to 'selected-window does not change this
>> behavior.
>
> What happens when you set `ido-default-buffer-method' to 'other-window?

Then I get window-splitting.  Should that affect frame-based behavior?

>> For some reason the gdb frame was split into two windows and I
>> accidentally deleted the wrong one and now the Separate IO is going
>> into the gdb buffer.
>
> Where IO goes to is not related to the window/buffer relationship.

I don't think it's related to the bug, it was just part of my narrative
describing the problem.

>> However, when I try to to switch back to the *gud* buffer, it
>> puts the point in a completely different window.
>
> What do you mean by this?  That the *gud* buffer is displayed in the
> wrong window?

In the wrong frame: for example, say *gud* originally was in frame 1;
then I accidentally switch buffers (so no frame displays the *gud*
buffer).  Then with the point in frame 1 I switch buffers and *gud* pops
up in frame 2.

>> I don't want *gud* in that frame, I want it in the one I'm trying to
>> put it in!  NOTE: THIS BEHAVIOR PERSISTS EVEN AFTER SWITCHING OUT OF
>> IDO-SWITCH-BUFFER BY PRESSING "C-b".
>
> What is C-b bound to in this situation?

C-b in ido-switch-buffer reverts to normal (non-ido) buffer-switching.
So if you start a buffer-switch with C-xb, the ido menu comes up; if you
press C-b you get the regular buffer switch prompt.

>> The buffer-switching behavior I submitted earlier also happens when
>> using the Buffers menu.
>
> Could you please try to run `display-buffer' with edebug to trace the
> behavior you observe?
>
> Usually this can happen only if (1) `pop-up-frames' is non-nil, (2)
> `display-buffer-reuse-frames' is non-nil, or (3) the windows on the
> selected frame are dedicated.

*gud* should be dedicated when I open the frame from the GDB menu;
unfortunately it doesn't "stay dedicated," it rather switches its
dedication to another frame Benedict Arnold-style.

Thanks,

Joel
-- 
Joel J. Adamson
Servedio Lab
University of North Carolina at Chapel Hill

FSF Member #8164
http://www.unc.edu/~adamsonj

[-- Attachment #2: Type: application/pgp-signature, Size: 229 bytes --]