From: martin rudalics <rudalics@gmx.at>
To: Tassilo Horn <tsdh@gnu.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 20189@debbugs.gnu.org
Subject: bug#20189: 25.0.50; Feature request: Alternative split-window-sensibly functions
Date: Thu, 26 Mar 2015 11:58:28 +0100 [thread overview]
Message-ID: <5513E654.3010501@gmx.at> (raw)
In-Reply-To: <87oange62o.fsf@gnu.org>
> To answer myself: it seems I actually want to use a minimum width of
> 80. That seems to supress any splits that result in windows smaller
> than 80 columns unless the width is explicitly given, e.g.,
>
> (setq window-min-width 80)
> (display-buffer (get-buffer "*Help*")
> '(display-buffer-pop-up-window
> (window-width . 10)))
>
> still splits although the new window is just 10 columns wide.
Not really. The window gets split because your frame is wide enough
(probably larger than 160 columns). The new window is 10 columns wide
because you explicitly asked for it via (window-width . 10).
martin
next prev parent reply other threads:[~2015-03-26 10:58 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
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 [this message]
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=5513E654.3010501@gmx.at \
--to=rudalics@gmx.at \
--cc=20189@debbugs.gnu.org \
--cc=eliz@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).