[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7368: Testcase
From: |
martin rudalics |
Subject: |
bug#7368: Testcase |
Date: |
Sat, 13 Nov 2010 09:32:45 +0100 |
User-agent: |
Thunderbird 2.0.0.21 (Windows/20090302) |
> C-h v pop-up-frames RET says:
>
> pop-up-frames's value is nil
>
> Documentation:
> Whether `display-buffer' should make a separate frame.
> If nil, never make a separate frame.
>
> However, a new frame *does* pop up for me after running the following code:
>
> (let ((foo (get-buffer-create "foo.el"))
> (bar (get-buffer-create "bar.el")))
> (switch-to-buffer foo)
> (delete-other-windows)
> (completion-at-point)
> (display-buffer bar t))
On my trunk Emacs your code produces a new window on the selected frame.
Apparently, some of your settings prevent it from splitting the selected
window and the second argument t means `display-buffer' must not reuse
the selected window. So `display-buffer' simply has no other choice but
making a new frame.
BTW, the snippet
(progn
(delete-other-windows)
(display-buffer (other-buffer) t))
should be sufficient for exhibiting the behavior you observe.
martin
- bug#7368: 23.2; Python interpreter buffer should never appear in separate frame, Andrey Paramonov, 2010/11/10
- bug#7368: Testcase, Андрей Парамонов, 2010/11/13
- bug#7368: Testcase,
martin rudalics <=
- bug#7368: Testcase, Андрей Парамонов, 2010/11/13
- bug#7368: Testcase, martin rudalics, 2010/11/13
- bug#7368: Testcase, Stefan Monnier, 2010/11/15
- bug#7368: Testcase, Андрей Парамонов, 2010/11/16
- bug#7368: Testcase, Stefan Monnier, 2010/11/16
- bug#7368: Testcase, martin rudalics, 2010/11/17
bug#7368: display-buffer a softly dedicated window, Андрей Парамонов, 2010/11/17