From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Windows' "split status" Date: Tue, 15 Nov 2011 17:39:04 +0800 Message-ID: <871ut9n2rr.fsf@gnu.org> References: <87vcqqoekt.fsf@gnu.org> <4EBD6B63.4050607@gmx.at> <87vcqq6utg.fsf@gnu.org> <4EBE4414.10009@gmx.at> <87d3cwr9hc.fsf@gnu.org> <4EBFA0AF.7000608@gmx.at> <87obwgatpy.fsf@gnu.org> <4EBFFBA5.1000309@gmx.at> <87hb26gdx8.fsf@gnu.org> <4EC213EA.4080304@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1321349966 15387 80.91.229.12 (15 Nov 2011 09:39:26 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 15 Nov 2011 09:39:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 15 10:39:22 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RQFUA-0001ys-7D for ged-emacs-devel@m.gmane.org; Tue, 15 Nov 2011 10:39:22 +0100 Original-Received: from localhost ([::1]:47561 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQFU5-0005P5-UW for ged-emacs-devel@m.gmane.org; Tue, 15 Nov 2011 04:39:17 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:56885) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQFU2-0005Oj-UM for emacs-devel@gnu.org; Tue, 15 Nov 2011 04:39:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQFU1-0002Mx-SP for emacs-devel@gnu.org; Tue, 15 Nov 2011 04:39:14 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:49719) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQFU1-0002Mt-QY for emacs-devel@gnu.org; Tue, 15 Nov 2011 04:39:13 -0500 Original-Received: from [155.69.16.229] (port=46348 helo=furball) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1RQFU0-0001fs-Ii; Tue, 15 Nov 2011 04:39:13 -0500 In-Reply-To: <4EC213EA.4080304@gmx.at> (martin rudalics's message of "Tue, 15 Nov 2011 08:25:30 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.91 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146038 Archived-At: martin rudalics writes: > But I wonder where and how people would want to use such a variable. For the same reason they'd use `window-nest'. My problem with `window-nest' is that the term is misleading: windows can still be "nested" even when `window-nest' is nil, in the sense that groups of live windows are nested within internal parent windows. A non-nil `window-nest' only means that a parent window can have only two children. That's why I think it's better to replace the "window nest status" concept with something like "the number of allowed children", which is more direct. Then there's no reason to limit to a binary choice between having two children and having unlimited children; we might as well specify the number of children as an arbitrary integer > 1. An alternative term might be window-combination-max-size. I don't care so much about the issue of whether to implement this with a window parameter rather than a special slot. The former seems conceptually cleaner, but the latter is fine if you think it's technically simpler. > For me it's neither trivial to understand nor trivial to implement. > So I'd be very glad if you gave it a stab. You can't break much - > earlier Emacsen always failed to recombine the windows from my > example. I'll take a look, though there are other a couple of other tasks I have to handle before getting to it.