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: moving window handling into lisp Date: Fri, 21 Aug 2009 14:22:06 +0200 Message-ID: <4A8E916E.3020109@gmx.at> References: <4A89AA46.6050502@gmx.de> <4A8BC2CD.5060303@gmx.de> <4A8BF3E0.5090304@gmx.at> <4A8D375D.9090905@gmx.de> <4A8D46DA.4090500@gmx.at> <4A8DA56F.7070908@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1250857368 12316 80.91.229.12 (21 Aug 2009 12:22:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Aug 2009 12:22:48 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 21 14:22:41 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MeT8T-0001kd-Jp for ged-emacs-devel@m.gmane.org; Fri, 21 Aug 2009 14:22:25 +0200 Original-Received: from localhost ([127.0.0.1]:59644 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeT8S-00085K-QH for ged-emacs-devel@m.gmane.org; Fri, 21 Aug 2009 08:22:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MeT8L-000856-Qo for emacs-devel@gnu.org; Fri, 21 Aug 2009 08:22:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MeT8H-00084U-72 for emacs-devel@gnu.org; Fri, 21 Aug 2009 08:22:17 -0400 Original-Received: from [199.232.76.173] (port=53690 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeT8G-00084O-TB for emacs-devel@gnu.org; Fri, 21 Aug 2009 08:22:12 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:35927) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MeT8F-0005VC-O6 for emacs-devel@gnu.org; Fri, 21 Aug 2009 08:22:12 -0400 Original-Received: (qmail invoked by alias); 21 Aug 2009 12:22:10 -0000 Original-Received: from 62-47-38-0.adsl.highway.telekom.at (EHLO [62.47.38.0]) [62.47.38.0] by mail.gmx.net (mp020) with SMTP; 21 Aug 2009 14:22:10 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX19K4QdzebVKFfe0+gRGk9XTyVUun7bUN6RzJuZ7ZZ sQyb+1K7oCWM40 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <4A8DA56F.7070908@gmx.de> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:114472 Archived-At: > The distributed fuzzy-machine cannot be simplified because it defends > itself by, well, being distributed. The weak point of that machine is the size_window routine which IIUC is called by most of these distributed components. >> > Me thinks there are much more thoughts spend on 'window-min-height' >> > now than there possibly were at the time when it was first introduced. >> >> Not really. Any window-manager has to deal with the possibility that a >> window gets to small when its parent-window shrinks. All we can do is >> make such cases occur rarely, in practice. > > Window-managers don't deal with shrinking parent windows. They deal > with fixed desktop/root windows. I obviously meant "any Emacs window-manager" here. I don't even know whether desktop window-managers use concepts like parent-windows or the split-window paradigm. > With individual applications it's called "layout-manager", which exist > in the various GUI toolkits. > > layout-managers are invisible containers that allow you to place > components like widgets or windows of other layout-managers within, > and to set a policy how these components are arranged, such as "box", > "grid", "flow", ... > > The concept of min-size exists too, though individually for each > component, and it actually means what it says, that is "keep this > thing at least that large". Consequently a case of "too small" can > never happen. So if a component doesn't fit it's iconified in some sense of that word? martin