[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#7368: Testcase
From: |
Андрей Парамонов |
Subject: |
bug#7368: Testcase |
Date: |
Sat, 13 Nov 2010 09:36:16 +0300 |
It turns out that the problem is not specific to Python mode. The
following minimal example reproduces it.
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))
Best wishes,
Andrey Paramonov
- bug#7368: 23.2; Python interpreter buffer should never appear in separate frame, Andrey Paramonov, 2010/11/10
- bug#7368: Testcase,
Андрей Парамонов <=
- bug#7368: Testcase, martin rudalics, 2010/11/13
- 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