From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: nicolas.despres@gmail.com, rpluim@gmail.com, juri@linkov.net,
emacs-devel@gnu.org
Subject: Re: Prefer to split along the longest edge
Date: Thu, 19 Dec 2024 11:21:29 +0200 [thread overview]
Message-ID: <86h670koyu.fsf@gnu.org> (raw)
In-Reply-To: <2aa16454-560c-4d3b-b3eb-e1b780d1b8d6@gmx.at> (message from martin rudalics on Thu, 19 Dec 2024 09:52:53 +0100)
> Date: Thu, 19 Dec 2024 09:52:53 +0100
> Cc: rpluim@gmail.com, juri@linkov.net, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> > If the split-size threshold of the window dimension determined by
> > `split-window-preferred-direction' specifies an integer, the
> > corresponding dimension of WINDOW is at least that large, then first
> > try splitting window in two along that dimension (one below the other
> > if splitting vertically, side by side if splitting horizontally).
> > The relevant threshold is `split-height-threshold' when splitting
> > vertically, and `split-width-threshold' when splitting horizontally.
> > If splitting along the preferred dimension fails, try splitting
> > WINDOW along the other dimension. If that also fails, and WINDOW is
> > the only window on its frame, try splitting WINDOW vertically
> > disregarding the value of `split-height-threshold'.
> >
> > If splitting succeeds, return the lower window if splitting
> > vertically, the right one if splitting horizontally. If splitting
> > fails, return nil.
> >
> > Martin, any comments or corrections to the above doc string?
>
> It's still hard to read for me. I'd write is as follows:
>
> The variable `split-window-preferred-direction' prescribes an order of
> directions in which Emacs should try to split WINDOW. If that order
> mandates to start with a vertical split and `split-height-threshold'
> specifies an integer that is at least as large a WINDOW's height, split
> WINDOW into two windows one below the other and return the lower one.
> If that order mandates to start with a horizontal split and
> `split-width-threshold' specifies an integer that is at least as large
> as WINDOW's width, split WINDOW into two windows side by side and return
> the one on the right.
>
> In either case, if the first attempt to split WINDOW fails, try to split
> the window in the other direction in the same manner as described above.
> If that attempts fail too and WINDOW is the only window on its frame,
> try splitting WINDOW into two windows one below the other disregarding
> the value of `split-height-threshold' and return the window on the
> bottom.
>
> Then the doc-string of 'split-window-preferred-direction' should say
> that its value implies an order of operations 'split-window-sensibly'
> will try and that that order may depend on the orientation of the frame.
> While the frame orientation is processed in 'split-window-sensibly', I
> wouldn't mention it there to avoid describing it twice.
>
> BTW the doc-string of 'split-window-preferred-direction' should also say
> that it applies to 'split-window-sensibly' only and not to any other
> functions that split windows.
Thanks, this is fine by me.
next prev parent reply other threads:[~2024-12-19 9:21 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 10:05 Prefer to split along the longest edge Nicolas Desprès
2024-12-14 11:30 ` Eli Zaretskii
2024-12-14 11:45 ` Nicolas Desprès
2024-12-14 12:34 ` Eli Zaretskii
2024-12-14 14:06 ` Nicolas Desprès
2024-12-14 14:55 ` Eli Zaretskii
2024-12-14 15:41 ` Nicolas Desprès
2024-12-14 17:16 ` martin rudalics
2024-12-14 17:33 ` Eli Zaretskii
2024-12-14 17:36 ` Eli Zaretskii
2024-12-14 18:35 ` Juri Linkov
2024-12-14 20:10 ` Nicolas Desprès
2024-12-15 7:34 ` Juri Linkov
2024-12-15 9:29 ` Nicolas Desprès
2024-12-16 7:55 ` Juri Linkov
2024-12-16 11:56 ` Nicolas Desprès
2024-12-16 17:14 ` Eli Zaretskii
2024-12-16 17:44 ` Juri Linkov
2024-12-16 19:07 ` Eli Zaretskii
2024-12-16 19:14 ` Juri Linkov
2024-12-16 19:53 ` Eli Zaretskii
2024-12-17 6:12 ` Nicolas Desprès
2024-12-17 7:40 ` Juri Linkov
2024-12-17 8:35 ` Nicolas Desprès
2024-12-17 9:02 ` martin rudalics
2024-12-17 9:09 ` Nicolas Desprès
2024-12-17 13:34 ` Eli Zaretskii
2024-12-18 10:05 ` martin rudalics
2024-12-18 14:12 ` Eli Zaretskii
2024-12-18 16:24 ` martin rudalics
2024-12-18 16:55 ` Eli Zaretskii
2024-12-18 17:41 ` martin rudalics
2024-12-18 18:41 ` Eli Zaretskii
2024-12-18 19:13 ` martin rudalics
2024-12-19 7:06 ` Juri Linkov
2024-12-18 17:25 ` Juri Linkov
2024-12-17 6:06 ` Nicolas Desprès
2024-12-17 12:52 ` Eli Zaretskii
2024-12-17 12:59 ` Eli Zaretskii
2024-12-17 13:12 ` Robert Pluim
2024-12-18 21:08 ` Nicolas Desprès
2024-12-19 6:39 ` Eli Zaretskii
2024-12-19 8:52 ` martin rudalics
2024-12-19 9:21 ` Eli Zaretskii [this message]
2024-12-19 16:20 ` Nicolas Desprès
2024-12-20 9:03 ` martin rudalics
2024-12-20 14:43 ` Nicolas Desprès
2024-12-20 15:05 ` Robert Pluim
2024-12-16 17:32 ` Juri Linkov
2024-12-17 9:01 ` martin rudalics
2024-12-17 13:32 ` Eli Zaretskii
2024-12-17 1:51 ` Liu Hui
2024-12-17 7:43 ` Juri Linkov
2024-12-17 8:27 ` Nicolas Desprès
2024-12-17 8:26 ` Nicolas Desprès
2024-12-16 17:15 ` [External] : " Drew Adams
2024-12-17 8:39 ` Nicolas Desprès
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=86h670koyu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=nicolas.despres@gmail.com \
--cc=rpluim@gmail.com \
--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).