From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: grischka Newsgroups: gmane.emacs.devel Subject: Re: moving window handling into lisp Date: Thu, 20 Aug 2009 21:35:11 +0200 Message-ID: <4A8DA56F.7070908@gmx.de> References: <4A89AA46.6050502@gmx.de> <4A8BC2CD.5060303@gmx.de> <4A8BF3E0.5090304@gmx.at> <4A8D375D.9090905@gmx.de> <4A8D46DA.4090500@gmx.at> 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 1250796946 23404 80.91.229.12 (20 Aug 2009 19:35:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Aug 2009 19:35:46 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 20 21:35:37 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 1MeDQ8-0004dn-BX for ged-emacs-devel@m.gmane.org; Thu, 20 Aug 2009 21:35:36 +0200 Original-Received: from localhost ([127.0.0.1]:45793 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeDQ7-0005D0-Q0 for ged-emacs-devel@m.gmane.org; Thu, 20 Aug 2009 15:35:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MeDQ1-0005Bo-0G for emacs-devel@gnu.org; Thu, 20 Aug 2009 15:35:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MeDPv-000561-DO for emacs-devel@gnu.org; Thu, 20 Aug 2009 15:35:27 -0400 Original-Received: from [199.232.76.173] (port=52208 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MeDPv-00055y-6q for emacs-devel@gnu.org; Thu, 20 Aug 2009 15:35:23 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:59355) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MeDPu-0000S8-4F for emacs-devel@gnu.org; Thu, 20 Aug 2009 15:35:23 -0400 Original-Received: (qmail invoked by alias); 20 Aug 2009 19:35:20 -0000 Original-Received: from p57A0970D.dip0.t-ipconnect.de (EHLO [192.168.1.2]) [87.160.151.13] by mail.gmx.net (mp003) with SMTP; 20 Aug 2009 21:35:20 +0200 X-Authenticated: #18588216 X-Provags-ID: V01U2FsdGVkX19Gvq0Yt0VGLoMNk5xt0zrkwUsacGh0umV0J30Ty7 G+RhHp8x2MtHjg User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) In-Reply-To: <4A8D46DA.4090500@gmx.at> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.71 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) 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:114461 Archived-At: martin rudalics wrote: > >> In principle, Emacs windows should not be less than `window-min-height' > >> lines tall. But an application can temporarily bind that variable to a > >> smaller value during resizing and leave around a window of less height. > >> Such windows usually don't harm when maximizing the frame but won't get > >> us back the previous state when switching back to normal. > > > > You can't blame packages that they go through any hack to defend > > their layout against the unpredictable interventions from the > > distributed fuzzy-machine, err... emacs window-management. > > We must defend such packages against any attempts to simplify Emacs > window-management at their cost. The distributed fuzzy-machine cannot be simplified because it defends itself by, well, being distributed. > > 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. 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. --- grischka > > martin >