From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel,gmane.emacs.help Subject: Re: frames dedicated to buffers, or, always see specific buffers in a specific frame Date: Mon, 15 Apr 2013 09:11:23 +0200 Message-ID: <516BA81B.3040904@gmx.at> References: <5167D3B7.2080408@gmx.at> <516816E9.1080206@gmx.at> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1366009900 12298 80.91.229.3 (15 Apr 2013 07:11:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Apr 2013 07:11:40 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, Stefan Monnier , emacs-devel@gnu.org To: =?ISO-8859-1?Q?Jo=E3o_T=E1vora?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 15 09:11:44 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1URdZn-00058F-0m for ged-emacs-devel@m.gmane.org; Mon, 15 Apr 2013 09:11:43 +0200 Original-Received: from localhost ([::1]:53056 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URdZm-0005nx-7T for ged-emacs-devel@m.gmane.org; Mon, 15 Apr 2013 03:11:42 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:47191) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URdZh-0005nf-9B for emacs-devel@gnu.org; Mon, 15 Apr 2013 03:11:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1URdZg-0005Ru-8C for emacs-devel@gnu.org; Mon, 15 Apr 2013 03:11:37 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:51642) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1URdZf-0005Rc-UP for emacs-devel@gnu.org; Mon, 15 Apr 2013 03:11:36 -0400 Original-Received: from mailout-de.gmx.net ([10.1.76.19]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0M8cOb-1UmlOg383H-00wGPM for ; Mon, 15 Apr 2013 09:11:33 +0200 Original-Received: (qmail invoked by alias); 15 Apr 2013 07:11:33 -0000 Original-Received: from 62-47-46-238.adsl.highway.telekom.at (EHLO [62.47.46.238]) [62.47.46.238] by mail.gmx.net (mp019) with SMTP; 15 Apr 2013 09:11:33 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+uUQYbCDau4SSAj0tnzdd3OWHsqhe73RXuaEMrIo 1TuUy49sJmgjgI In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:158914 gmane.emacs.help:90163 Archived-At: >> So for making this general purpose you should use `pop-to-buffer' >> instead of `display-buffer'. > > Yes, that works too. Why exactly is this more general purpose? I meant that if you really want to use this as a subtitute for `switch-to-buffer' you should make sure the window and frame get selected. They don't necessarily using `display-buffer' alone. > Also, ido has these `ido-default-buffer-method' and > `ido-default-file-method' that can be set to various options to > control how buffer appears. > > But the way these options implemented does not bring them all to > `display-buffer', which sometimes precludes user's control. Should't > they be implemented via `display-buffer-alist', keeping any of the > user's entries on top? Doesn't setting `ido-default-buffer-method' to `display' work? Maybe we could add `pop-to-buffer' to the default methods. > Pity. But what about making `switch-to-buffer' delegate to > `display-buffer' too? It could dinamically bind `display-buffer-alist' > to display and select the buffer, but keeping any existing entries > (probably set by the user, or other programs) on top. > > If that resulted in `switch-to-buffer' not switching to the buffer's > window, it could not be considered unexpected behaviour, since > ultimately the user set `display-buffer-alist' himself. The basic idea of the `switch-to-buffer' functions is to bypass the `display-buffer' customizations. That is, by default you display a buffer in a certain manner but always can use `switch-to-buffer' to override that default behavior. martin