From: "N. Jackson" <nljlistbox2@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
emacs-devel@gnu.org, Roland Winkler <winkler@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
Date: Thu, 13 Sep 2018 09:07:59 -0400 [thread overview]
Message-ID: <87r2hxv93k.fsf@moondust.localdomain> (raw)
In-Reply-To: <5B9A1599.2060800@gmx.at> (martin rudalics's message of "Thu, 13 Sep 2018 09:45:29 +0200")
At 09:45 +0200 on Thursday 2018-09-13, martin rudalics wrote:
>
>> If there was a function (frame-split-biggest-window FRAME SIZE SIDE
>> PIXELWISE) to split the "biggest" [*] window in the frame, then
>> neither BBDB nor any other Elisp code would need to keep reinventing
>> this wheel.
>>
>> (The other two functions, more for interactive use, would be
>> `frame-split-biggest-window-below' and
>> `frame-split-biggest-window-right'.)
>>
>> [*] To find the "biggest" window when splitting below, find the
>> tallest window or windows and split the widest of them; when
>> splitting right, find the widest window or windows and split the
>> tallest of them.
>
> We have a number of options for that. One of them is the option
> 'split-window-preferred-function' (a misnomer) which is by default set
> to 'split-window-sensibly'. Consult their definitions first. The
> latter's behavior is guided by the options 'split-height-threshold'
> and 'split-width-threshold' (two more misnomers) . Together, these
> should provide a boilerplate for writing your own function which you
> can then put into 'display-buffer-alist'.
What's missing with these functions is that they start from a given
window. What's needed is functionality that looks at all the windows
on (in?) the frame and chooses which one to split.
next prev parent reply other threads:[~2018-09-13 13:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 20:31 customize location and shape of a new window in a frame Roland Winkler
2018-09-11 21:22 ` Eric Abrahamsen
2018-09-12 19:36 ` N. Jackson
2018-09-12 20:12 ` Eric Abrahamsen
2018-09-12 23:21 ` Suggesting `frame-split-biggest-window' " N. Jackson
2018-09-13 7:45 ` martin rudalics
2018-09-13 13:07 ` N. Jackson [this message]
2018-09-14 8:31 ` martin rudalics
2018-09-13 16:33 ` Eric Abrahamsen
2018-09-14 8:33 ` martin rudalics
2018-09-14 16:56 ` Eric Abrahamsen
2018-09-15 8:17 ` martin rudalics
2018-09-14 5:17 ` Roland Winkler
2018-09-14 8:33 ` martin rudalics
2018-09-14 12:01 ` Stefan Monnier
2018-09-15 4:12 ` Roland Winkler
2018-09-15 4:58 ` Drew Adams
2018-09-15 8:18 ` martin rudalics
2018-09-15 16:34 ` Roland Winkler
2018-09-15 18:34 ` Stefan Monnier
2018-09-15 19:21 ` Roland Winkler
2018-09-15 12:24 ` N. Jackson
2018-09-15 14:56 ` Stefan Monnier
2018-09-15 0:46 ` Richard Stallman
2018-09-15 8:17 ` martin rudalics
2018-09-16 3:14 ` Richard Stallman
2018-09-16 19:05 ` John Yates
2018-09-16 19:22 ` Eli Zaretskii
2018-09-16 20:30 ` Drew Adams
2018-09-13 16:38 ` Eric Abrahamsen
2018-09-12 14:54 ` Stefan Monnier
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=87r2hxv93k.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
--cc=winkler@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).