From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: why pop-to-buffer has this ugly behavior? Date: Thu, 22 Jan 2004 12:35:49 -0700 Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <40102615.7070306@yahoo.com> References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1074801053 18540 80.91.224.253 (22 Jan 2004 19:50:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Jan 2004 19:50:53 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jan 22 20:50:41 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ajkqe-000736-01 for ; Thu, 22 Jan 2004 20:50:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1Ajkpx-0001Vd-Bs for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Jan 2004 14:49:57 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 26 Original-NNTP-Posting-Host: 170.207.51.80 Original-X-Trace: news.uni-berlin.de 1074800148 21363636 170.207.51.80 ([82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Original-Xref: shelby.stanford.edu gnu.emacs.help:120336 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:16280 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:16280 Klaus Berndl wrote: > I have wondered why here pop-to-buffer does not split the unsplitted window in > my frame. Then i have tested the following (The value of `pop-up-windows' is > t!): > > (pop-to-buffer (get-buffer-create "*BlaBlaBla*")) > > which splits an unsplitted window in 2 windows - well! > > (pop-to-buffer (get-buffer-create "*Customization*")) > > which does not split an unsplitted windows in 2 - very bad and ugly! > > Conclusion: pop-up-buffer must have somewhere in the c-code - or maybe > display-buffer) but anyway - some logic which decides dependent on the > buffer-name if the window should be splitted or not?! I write this not to the > bug-list because it is not really a bug but it is a strong violation of one > of the most important design-principles: "Separation of concerns". C-h v same-window-regexps -- Kevin Rodgers