From: "Андрей Парамонов" <cmr.pent@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 7368@debbugs.gnu.org
Subject: bug#7368: display-buffer a softly dedicated window
Date: Thu, 18 Nov 2010 13:36:59 +0300 [thread overview]
Message-ID: <AANLkTimz3m8C1-Ax2mp8hcqdJnFPVVyk6q_uWADMLEG7@mail.gmail.com> (raw)
In-Reply-To: <4CE4FF80.4080404@gmx.at>
2010/11/18 martin rudalics <rudalics@gmx.at>:
>> comint.el forces *Completions* to close and shows the interpreter
>> immediately, in its place. That's what I want, exactly. Showing the
>> interpreter in place of *Completions* would have the same effect, so
>> it's what I want, too.
>
> I've looked into comint.el. It's apparently based on window
> configurations and restores the old configuration when you do
> `choose-completion' or type SPACE. I don't see where it deletes the
> window when you do something else. Very contrived code.
If you are interested you may check the example I provided in my
recent emacs.devel thread. *Completions* is somehow closed before
comint-dynamic-list-completions is finished
(comint-dynamic-list-completions doesn't exit immediately upon showing
*Completions*).
> Hm... What about setting `display-buffer-function' to something like:
>
> (defun my-display-buffer (buffer flag)
> (let (window display-buffer-function)
> (when (and (= (length (window-list)) 2)
> (setq window (get-buffer-window "*Completions*")))
> (set-window-dedicated-p window nil))
> (display-buffer buffer flag)))
>
Hm, nice idea. But isn't display-buffer-function called from
display-buffer (infinite recursion)? I'll check it when I get to my
Emacs box.
Best wishes,
Andrey Paramonov
next prev parent reply other threads:[~2010-11-18 10: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 ` bug#7368: Testcase Андрей Парамонов
2010-11-13 8:32 ` 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 ` Андрей Парамонов [this message]
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=AANLkTimz3m8C1-Ax2mp8hcqdJnFPVVyk6q_uWADMLEG7@mail.gmail.com \
--to=cmr.pent@gmail.com \
--cc=7368@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).