From: "Jarosław Rzeszótko" <sztywny@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Controlling which windows can be selected by display-buffer-pop-up-window
Date: Sun, 22 Dec 2013 16:56:28 +0100 [thread overview]
Message-ID: <CAHnYAZZHHsGi9LjtruqyfWzHnhKp3XQ30E=-i84jQ7A4pwKCBA@mail.gmail.com> (raw)
In-Reply-To: <52B70745.10201@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi,
Thank you, that seems to work perfectly well!
Cheers,
Jarosław Rzeszótko
2013/12/22 martin rudalics <rudalics@gmx.at>
> > Is there any chance a more flexible mechanism for controlling which
> window
> > is chosen to be split when a new buffer is about to displayed could make
> it
> > into Emacs? I have been trying to implement a way to keep a toggleable
> > terminal or compilation window at the bottom of an Emacs frame, that is
> > only a few lines high and is never split or deleted unless the users
> > requests it - I think this is a perfectly reasonable feature many people
> > would like, and one present in many environments those days. Currently,
> to
> > the extent I managed to learn, implementing a window that consistently
> > keeps a fixed position and size and is never split, is possible only in
> two
> > ways, one is a really dirty hack, and the second one requires
> > reimplementing a lot of the mechanisms in window.el.
>
> To avoid that a window is split, fix its buffer's height (see the
> variable `window-size-fixed').
>
> To show a window continuously at the bottom of a frame, use the function
> `display-buffer-in-side-window' with a 'bottom argument.
>
> No dirty hacks needed ;-)
>
> martin
>
[-- Attachment #2: Type: text/html, Size: 1740 bytes --]
prev parent reply other threads:[~2013-12-22 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 18:18 Controlling which windows can be selected by display-buffer-pop-up-window Jarosław Rzeszótko
2013-12-22 15:37 ` martin rudalics
2013-12-22 15:56 ` Jarosław Rzeszótko [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='CAHnYAZZHHsGi9LjtruqyfWzHnhKp3XQ30E=-i84jQ7A4pwKCBA@mail.gmail.com' \
--to=sztywny@gmail.com \
--cc=emacs-devel@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).