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: split-window-preferred-function Date: Sun, 06 Apr 2008 00:02:42 +0200 Message-ID: <47F7F702.9060900@gmx.at> References: <005d01c89719$de92d340$1f45fe91@j4f3n1> <47F79DEE.6000806@gmx.at> <010001c8974b$da82b680$130990d4@j4f3n1> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1207434422 4151 80.91.229.12 (5 Apr 2008 22:27:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Apr 2008 22:27:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 06 00:27:35 2008 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 1JiGrC-0005bR-Rh for ged-emacs-devel@m.gmane.org; Sun, 06 Apr 2008 00:27:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JiGqa-0006rY-1T for ged-emacs-devel@m.gmane.org; Sat, 05 Apr 2008 18:26:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JiGph-0005ku-Mv for emacs-devel@gnu.org; Sat, 05 Apr 2008 18:25:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JiGpg-0005je-VG for emacs-devel@gnu.org; Sat, 05 Apr 2008 18:25:57 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JiGpg-0005jJ-MK for emacs-devel@gnu.org; Sat, 05 Apr 2008 18:25:56 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1JiGpg-0007St-D3 for emacs-devel@gnu.org; Sat, 05 Apr 2008 18:25:56 -0400 Original-Received: (qmail invoked by alias); 05 Apr 2008 22:25:55 -0000 Original-Received: from 62-47-52-214.adsl.highway.telekom.at (EHLO [62.47.52.214]) [62.47.52.214] by mail.gmx.net (mp036) with SMTP; 06 Apr 2008 00:25:55 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1/l1jR3LhnlalgrQuTKaiLOSQdwMVLEmG/h5XUhLh jx8B40ZG/bn+h7 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en In-Reply-To: <010001c8974b$da82b680$130990d4@j4f3n1> X-Y-GMX-Trusted: 0 X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:94450 Archived-At: > Actually elscreen has a separate "layout creation" mode (although it > is not as easy to use, and also IMO redundant, it could as well just > live record user changes made in the "real" frame). > > But yes, you can save everything to disk, anytime. Means it allows > to get used to something, body-language wise. I don't know much about elscreen. Can you tell me the name of the package / function(s) implementing "layout creation"? > Option three: Allow zero-width and zero-height windows. I thought about that already although I personally dislike hidden windows. > Such there is actually no need for the code to *ever* create > new windows automatically, because the "tree" is already either > predefined and/or customized. Just the sizes aren't filled in always. Currently there is no predefined tree. We still would have to recursively split the root window in some way. > All windows would have some target class-properties, like "file", > "help", "commandline", so if some buffer needs to be shown, the > buffer/window-manager (which of I assume emacs has one) can apply > some logic which buffer to show in what window. The target class property already exists in some sense - certain buffers can be always shown in the same windows. The buffer/window manager is `display-buffer' which sets up the appropriate window for a buffer. > (window > :name "bottom-display" > :content-classes '("*help*" "*output*" ...) > ... > :visible 'if-needed Yes. We should enumerate useful configurations where, for example, the bottom-most window is shared by help and compiler output (just that I sometimes want to display *help* and *info* in one and the same frame). In any case, we have to design rules for making these configurations appear on the display. > Still the user is allowed to modify the tree anytime of course, > by split-window or whatever. Just not the code. And by delete-window, I presume. Anyway, restoring a configuration that existed already is less difficult.