From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: pop-up-windows value to force a new window
Date: Tue, 5 Sep 2006 14:33:38 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMKEBLCLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <33742.128.165.123.18.1157486375.squirrel@webmail.lanl.gov>
> I don't see a good way to force `display-buffer' and related
> functions to always use another window, even when there is
> more than one window displayed currently. Is there some way
> (besides defining `display-buffer-function'
> in such a way that it does this)?
First, you need to define what "always use another window"
means. What if
the current frame is divided into so many windows (or is itself
so small)
that no splitting can occur because of the minimum window size
variables?
What if the current frame is unsplittable (where you shouldn't split it
automatically), or worse is a minibuffer-only frame that you -can't-
split?
Yes, of course. Before heading down the highway, corner cases would need to
be dealt with.
> This would let Lisp code, for example, bind to that value, and be sure
> that
> `display-buffer' etc. will always create a new window. Subsequently
> deleting
> that window will not leave fewer windows than before the display. IOW,
> this
> would let you use `display-buffer' to always pop up an extra window.
If you want to "not leave fewer windows", what you probably want is to
restore the window configuration. If that's what you want, just do it:
use `current-window-configuration' and
`set-window-configuration'. (There
are a few other useful related functions which can be found
with Apropos.)
If it interests, I have written a small "temporary window
configurations"
package which aims to automate that process.
I don't really recall what I was trying to do. I believe that I started with
`with-output-to-temp-buffer', and I wanted to have it always open a new
window, so deleting that window would not reduce the original config. IIRC,
I tried to use `save-window-configuration' with it, but things didn't
proceed as I wanted. I don't remember the details, and I don't have time now
to look into it.
prev parent reply other threads:[~2006-09-05 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 20:38 pop-up-windows value to force a new window Drew Adams
2006-09-02 21:20 ` Eli Zaretskii
2006-09-02 21:53 ` Drew Adams
2006-09-02 22:25 ` Chong Yidong
2006-09-03 21:33 ` Kim F. Storm
2006-09-05 19:59 ` Stuart D. Herring
2006-09-05 21:33 ` Drew Adams [this message]
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=EIENLHALHGIMHGDOLMIMKEBLCLAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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).