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: Window configurations Date: Wed, 12 May 2010 20:33:43 +0200 Message-ID: <4BEAF487.1070605@gmx.de> References: 4BE900E7.3090402@gmx.at <4BE96186.7060504@gmx.de> <4BEA74B7.2070609@gmx.at> <4BEA8D2D.4090109@gmx.de> <4BEAA73F.4060608@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: dough.gmane.org 1273690698 9093 80.91.229.12 (12 May 2010 18:58:18 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 12 May 2010 18:58:18 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 12 20:58:16 2010 connect(): No such file or directory 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.69) (envelope-from ) id 1OCH8H-0000Lp-Kk for ged-emacs-devel@m.gmane.org; Wed, 12 May 2010 20:58:13 +0200 Original-Received: from localhost ([127.0.0.1]:34286 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCH8H-0004jL-3S for ged-emacs-devel@m.gmane.org; Wed, 12 May 2010 14:58:13 -0400 Original-Received: from [140.186.70.92] (port=48360 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCGzG-0007U1-BG for emacs-devel@gnu.org; Wed, 12 May 2010 14:48:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OCGkp-0006Kd-4K for emacs-devel@gnu.org; Wed, 12 May 2010 14:33:59 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:53524) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OCGko-0006K9-Lu for emacs-devel@gnu.org; Wed, 12 May 2010 14:33:59 -0400 Original-Received: (qmail invoked by alias); 12 May 2010 18:33:55 -0000 Original-Received: from unknown (EHLO [10.62.25.127]) [82.113.106.188] by mail.gmx.net (mp026) with SMTP; 12 May 2010 20:33:55 +0200 X-Authenticated: #18588216 X-Provags-ID: V01U2FsdGVkX1+GgxVkzgeGyzSZgRAvX54vc3x2A0SapTZzYPgWC8 jOw6hpp0WpcGS+ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: <4BEAA73F.4060608@gmx.at> X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.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:124728 Archived-At: martin rudalics wrote: > > One mistake is to cater for windows on the same level of generality as you > > obviously do for low level lisp. Of course you want functions "cons" etc. > > to allow generation of arbitrarily complex lisp structures, but it cannot > > be the point of "split-window" to generate arbitrarily complex > > window-trees, > > I'm not sure whether I get your point. But windows are first class > citizens in the Elisp world and `split-window' must be allowed to create > arbitrarily complex window trees on an arbitrarily complex machine. Which does not mean that any feature can be allowed to use split-window as it happens to think. > > (and anyway the result of some such is not a "window-configuration" but at > > most a "window-state"). > > In my book a "window configuration" is "the state of all windows". In my book configuration is rules and state is result from their application (together with other conditions). Conflating the both will just produce a classical chicken & egg problem. > > The other mistake is _not_ to cater for windows on the same level of > > _reliability_ as you obviously do for low level lisp. "Cons" doesn't work > > "intuitively" in the sense of "heuristically", and one has to accept that > > there is no other "intuitively right window" to display some buffer except > > the exactly one defined location where the user wants to see it. > > The question which buffer I want to display must be solved heuristically > because it's too complex to analyze the intentions of each and every > Emacs user (and possibly provide the necessary customizations) in Elisp. There is no need to guess intentions if users were allowed to express them (and emacs was disallowed to ignore them). > The heuristics should guess the "intuitively right window" in a way > which can be roughly measured by the number of postings criticizing its > implementation. You want "display-buffer" query the emacs bug tracker? ;) > > And that is actually what "window-configuration" can only mean: A way to > > define windows for particular content (aka. buffers) _before_ the window > > exists physically. > > IIUC that's what packages like ECB do. And ECB leaves it to Emacs and > its users to modify the configuration/state of the edit area. > > > From then on it is easy, you just need to tell "display-buffer" to use > > that > > window rsp. to generate it if it doesn't yet exist. > > martin > --- grischka