From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: pop-to-buffer doesn't honnor pop-up-frames? Date: Mon, 08 Dec 2003 21:42:43 GMT Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1070920361 5135 80.91.224.253 (8 Dec 2003 21:52:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 8 Dec 2003 21:52:41 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Dec 08 22:52:37 2003 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 1ATTIz-0004HG-00 for ; Mon, 08 Dec 2003 22:52:37 +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 1ATU9h-0000QG-A4 for geh-help-gnu-emacs@m.gmane.org; Mon, 08 Dec 2003 17:47:05 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!logbridge.uoregon.edu!snoopy.risq.qc.ca!charlie.risq.qc.ca!53ab2750!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 32 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-NNTP-Posting-Host: 132.204.24.42 Original-X-Complaints-To: abuse@umontreal.ca Original-X-Trace: charlie.risq.qc.ca 1070919763 132.204.24.42 (Mon, 08 Dec 2003 16:42:43 EST) Original-NNTP-Posting-Date: Mon, 08 Dec 2003 16:42:43 EST Original-Xref: shelby.stanford.edu gnu.emacs.help:119132 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:15070 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:15070 >> > Is this a bug? The docstring for pop-to-buffer says it uses >> > display-buffer internally. But when I have pop-up-frames set to t, >> > pop-to-buffer doesn't seem to be affected: it splits the current window. >> >> I know it works: I use it all the time. >> But the behavior of display-buffer (and thus pop-to-buffer) is complex >> and depends on many things. Does it fail to work for some specific buffers >> or for all of them ? > Huh, it seems to only sometimes pop up a new frame. For example, M-x > info doesn't pop up a new frame, it takes the current frame. I'm > trying to get a usable setup with buffers in their own frames. If it stays in the same window it's probably because it uses switch-to-buffer instead of pop-to-buffer (a common problem despite my years of effort) or because of the stupid same-window-buffer-names or same-window-regexps. But your original post mentioned splitting the current window, which doesn't ring a bell (although I don't rule out having seen it already). > You menionted that you have such a setup, would you mind sharing > what's in your .emacs that does this? I can't seem to get it to > reliably work more than 75% of the time. I can't even remember which part of my .emacs is relevant and I have a vested interest in finding out what problems normal users still encounter when trying to set up such a config. So I'd rather help you along than give you my solution. Stefan