From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Windows' "split status" Date: Sun, 13 Nov 2011 18:17:25 +0100 Message-ID: <4EBFFBA5.1000309@gmx.at> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1321204659 20883 80.91.229.12 (13 Nov 2011 17:17:39 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 13 Nov 2011 17:17:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 13 18:17:35 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 1RPdgV-00089p-7A for ged-emacs-devel@m.gmane.org; Sun, 13 Nov 2011 18:17:35 +0100 Original-Received: from localhost ([::1]:34972 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RPdgU-0001Dq-BA for ged-emacs-devel@m.gmane.org; Sun, 13 Nov 2011 12:17:34 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:48354) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RPdgR-0001DZ-IW for emacs-devel@gnu.org; Sun, 13 Nov 2011 12:17:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RPdgQ-0003s8-3A for emacs-devel@gnu.org; Sun, 13 Nov 2011 12:17:31 -0500 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:59938) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RPdgP-0003s0-LU for emacs-devel@gnu.org; Sun, 13 Nov 2011 12:17:30 -0500 Original-Received: (qmail invoked by alias); 13 Nov 2011 17:17:27 -0000 Original-Received: from 62-47-44-121.adsl.highway.telekom.at (EHLO [62.47.44.121]) [62.47.44.121] by mail.gmx.net (mp051) with SMTP; 13 Nov 2011 18:17:27 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX18aql4J8rgasqoZWAQj8UFJidADiRozxVrRJc304Z WZZoZDPVjEtCMa User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <87obwgatpy.fsf@gnu.org> X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 213.165.64.23 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:146031 Archived-At: > How about a variation on this scheme: introduce a `max-children' window > parameter which, if non-nil, determines the maximum number of children > that a window can have (relevant only for internal windows). For atomic > and side windows, this window parameter would be explicitly set to 2. > When the window parameter is nil or absent, the actual value would be > determined by a user option `window-max-children'. > > That would make the behavior more explicit, I think. Do I understand correctly that you want to get rid of the "nest" slot in the window structur? The problem with window parameters is that I currently do save them together with a window configuration and restore them when restoring the configuration. Earlier, Stefan didn't want to do that and I'd like to revert the current behavior at any time when problems arise. This would mean, however, that when you have a nested window, dissolve it within a window excursion, and restore the initial configuration, the nesting would get lost. So I'd rather be on the safe side in this regard. OTOH, it's not entirely trivial to handle `window-max-children' during recombination. Suppose you have a configuration like ------------------- | | | W3 | W4 | | W1 | W2 |---------| | | | W5 | ------------------- the user has set `window-max-children' to 3 and deletes W5. How should recombine_windows proceed? martin