From: martin rudalics <rudalics@gmx.at>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 20189@debbugs.gnu.org
Subject: bug#20189: 25.0.50; Feature request: Alternative split-window-sensibly functions
Date: Tue, 24 Mar 2015 14:30:06 +0100 [thread overview]
Message-ID: <551166DE.9070007@gmx.at> (raw)
In-Reply-To: <87egoebp60.fsf@gnu.org>
>>> With that and a maximized frame of size 269x82, I'd eventually end up
>>> with three side-by-side windows each of size 86x82.
>>
>> Interesting. What is your value of `window-combination-resize'?
>
> I didn't know that, so it has the default value nil.
Then how comes you "eventually end up with three side-by-side windows
each of size 86x82"? By default you should get one window with 135
columns and two windows with 67 columns, approximately.
> Reading its docs I
> get the impression that I want that to be t instead, and to have it
> effective, I'd also need to set `window-combination-limit' to nil.
>
> But with
>
> (setq window-combination-resize t
> window-combination-limit nil) ;; was window-size before
>
> and a single 269x82 window, I still get a horizontal split first
> (forming a horizontal combination IIUC) and then a vertical split.
Yes - these are unrelated. `split-window-sensibly' controls the
"split-direction".
I share most of your concerns. But I'm not sure though where to put
a/the solution.
martin
next prev parent reply other threads:[~2015-03-24 13:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:18 bug#20189: 25.0.50; Feature request: Alternative split-window-sensibly functions Tassilo Horn
2015-03-24 10:51 ` martin rudalics
2015-03-24 11:39 ` Tassilo Horn
2015-03-24 13:30 ` martin rudalics [this message]
2015-03-24 14:59 ` Tassilo Horn
2015-03-25 8:23 ` martin rudalics
2015-03-25 9:41 ` Tassilo Horn
2015-03-26 10:58 ` martin rudalics
2015-03-26 11:01 ` Tassilo Horn
2015-03-26 13:47 ` martin rudalics
2015-03-26 14:18 ` Stefan Monnier
2015-03-26 14:31 ` martin rudalics
2015-03-27 18:26 ` Stefan Monnier
2015-03-26 15:15 ` Tassilo Horn
2015-03-26 16:04 ` martin rudalics
2015-03-24 17:05 ` Eli Zaretskii
2015-03-25 7:00 ` Tassilo Horn
2015-03-25 8:24 ` martin rudalics
2015-03-25 17:25 ` Eli Zaretskii
2015-03-25 19:33 ` Tassilo Horn
2015-03-25 19:38 ` Eli Zaretskii
2015-03-26 4:27 ` Tassilo Horn
2015-03-26 10:58 ` martin rudalics
2015-03-26 16:29 ` Eli Zaretskii
2015-03-25 8:23 ` martin rudalics
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=551166DE.9070007@gmx.at \
--to=rudalics@gmx.at \
--cc=20189@debbugs.gnu.org \
--cc=tsdh@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).