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: Fri, 19 Nov 2010 09:30:47 +0300 [thread overview]
Message-ID: <AANLkTi=WVT6wOrxadY0gTDCiE4UHx4JnS2iJoj3RnUX5@mail.gmail.com> (raw)
In-Reply-To: <4CE52824.4050304@gmx.at>
I've checked out window-pub and played with it bit. Basically,
everything worked great for me so far (note: I use default window
options). Didn't notice any regressions. The problem with
*Completions* is gone because in window-pub *Completions* is not
dedicated :-) Also, I liked that many functions moved from C to Lisp
(one can explore and tweak them much easier).
As a temporary solution to the bug I now use the following code. It
has some minor issues (i.e. if *Completions* is above code buffer, and
I switch to interpreter, code buffer would come above and interpreter
buffer would come below), but I can definitely live with it. However,
proper upstream fix would still be very welcome.
(defun my-display-buffer (buffer flag)
(when (not (eq (buffer-name buffer) "*Completions*"))
(let ((completions-window (get-buffer-window "*Completions*")))
(when completions-window
(quit-window nil completions-window))))
(let (display-buffer-function)
(display-buffer buffer flag)))
(setq display-buffer-function 'my-display-buffer)
Thanks for your support,
Andrey Paramonov
next prev parent reply other threads:[~2010-11-19 6:30 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 ` Андрей Парамонов
2010-11-18 13:20 ` martin rudalics
2010-11-19 6:30 ` Андрей Парамонов [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=WVT6wOrxadY0gTDCiE4UHx4JnS2iJoj3RnUX5@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.