unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Kupfer <m.kupfer@acm.org>
To: emacs-devel@gnu.org
Subject: the window tree, window-combination-limit
Date: Wed, 30 Nov 2016 21:08:09 -0800	[thread overview]
Message-ID: <20822.1480568889@allegro.localdomain> (raw)

The discussion for bug 25055 mentioned the variable
window-combination-resize.  Since I frequently use balance-windows after
splitting or deleting a window, window-combination-resize looked worth
investigating.  Its docstring (in 25.1.90) says

  This variable takes no effect if the variable ‘window-combination-limit’ is
  non-nil.

so I also looked at window-combination-limit.  I have a couple questions
as a result.

The default value for window-combination-limit is 'window-size', which
is documented as

  ‘window-size’ means that splitting a window for displaying a buffer
      makes a new parent window provided ‘display-buffer’ is supposed to
      explicitly set the window’s size due to the presence of a
      ‘window-height’ or ‘window-width’ entry in the alist used by
      ‘display-buffer’.  Otherwise, this value is handled like nil.

After several attempts I can parse the first sentence, but I'm having
trouble understanding its significance.

More generally, as a user, should I care about the window tree and
parent windows?  A web search on

  emacs parent window

gives me several hits in the Emacs Lisp Reference Manual, but I don't
see anything about the window tree in the Emacs Manual.  Can someone
explain the different values for window-combination-limit in terms of
what I would see as a user?

Thanks for any illumination.

mike

"I understand just a little
No comprende--it's a riddle" --Wall of Voodoo, "Mexican Radio"



             reply	other threads:[~2016-12-01  5:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  5:08 Mike Kupfer [this message]
2016-12-01 10:09 ` the window tree, window-combination-limit martin rudalics
2016-12-04 21:45   ` Mike Kupfer
2016-12-05 16:43   ` John Yates
2016-12-05 16:59     ` Eli Zaretskii

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=20822.1480568889@allegro.localdomain \
    --to=m.kupfer@acm.org \
    --cc=emacs-devel@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).