From: "Андрей Парамонов" <cmr.pent@gmail.com>
To: 7368@debbugs.gnu.org
Subject: bug#7368: Testcase
Date: Sat, 13 Nov 2010 09:36:16 +0300 [thread overview]
Message-ID: <AANLkTimAqX3pDL-gukU4BHoY4Gj3_K0fREj275ARd9tj@mail.gmail.com> (raw)
In-Reply-To: <87y690q1qa.fsf@neo.paramonovs>
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
next prev parent reply other threads:[~2010-11-13 6:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 21:59 bug#7368: 23.2; Python interpreter buffer should never appear in separate frame Andrey Paramonov
2010-11-13 6:36 ` Андрей Парамонов [this message]
2010-11-13 8:32 ` bug#7368: Testcase martin rudalics
2010-11-13 8:47 ` Андрей Парамонов
2010-11-13 9:55 ` martin rudalics
2010-11-15 22:42 ` Stefan Monnier
2010-11-16 20:19 ` Андрей Парамонов
2010-11-16 21:25 ` Stefan Monnier
2010-11-17 9:46 ` martin rudalics
2010-11-17 8:57 ` bug#7368: display-buffer a softly dedicated window Андрей Парамонов
2010-11-17 9:46 ` martin rudalics
2010-11-17 9:58 ` Андрей Парамонов
2010-11-17 14:16 ` martin rudalics
2010-11-17 15:09 ` Андрей Парамонов
2010-11-17 17:13 ` martin rudalics
2010-11-17 18:55 ` Андрей Парамонов
2010-11-18 8:03 ` martin rudalics
2010-11-18 8:32 ` Андрей Парамонов
2010-11-18 9:07 ` martin rudalics
2010-11-18 9:40 ` Андрей Парамонов
2010-11-18 10:27 ` martin rudalics
2010-11-18 10:36 ` Андрей Парамонов
2010-11-18 13:20 ` martin rudalics
2010-11-19 6:30 ` Андрей Парамонов
2011-07-13 2:07 ` Glenn Morris
2011-07-13 6:24 ` martin rudalics
2011-07-13 6:45 ` Glenn Morris
2011-07-13 8:37 ` martin rudalics
2011-07-13 16:07 ` Glenn Morris
2014-12-25 10:55 ` martin rudalics
2010-11-18 14:18 ` Stefan Monnier
2010-11-17 13:10 ` Stefan Monnier
2010-11-18 20:56 ` Lennart Borgman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimAqX3pDL-gukU4BHoY4Gj3_K0fREj275ARd9tj@mail.gmail.com \
--to=cmr.pent@gmail.com \
--cc=7368@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).