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: switch-to-buffer: for interactive use only Date: Sat, 09 Jul 2011 10:45:46 +0200 Message-ID: <4E18153A.3060306@gmx.at> References: <0aiprg76eu.fsf@fencepost.gnu.org> <87hb6zt8rg.fsf@stupidchicken.com> <8739ihlsry.fsf@stupidchicken.com> <4E16A728.5040002@gmx.at> <4E170E48.5040408@gmx.at> <4E173412.3090804@gmx.at> <87d3hkmt0k.fsf@stupidchicken.com> <87vcvcmr8y.fsf@stupidchicken.com> <87zkkokwp7.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1310201241 32097 80.91.229.12 (9 Jul 2011 08:47:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 9 Jul 2011 08:47:21 +0000 (UTC) Cc: Juanma Barranquero , Chong Yidong , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 09 10:47:17 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QfTBz-0000ag-0W for ged-emacs-devel@m.gmane.org; Sat, 09 Jul 2011 10:47:15 +0200 Original-Received: from localhost ([::1]:58067 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfTBy-0000r0-28 for ged-emacs-devel@m.gmane.org; Sat, 09 Jul 2011 04:47:14 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:40526) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QfTAf-0000ax-MO for emacs-devel@gnu.org; Sat, 09 Jul 2011 04:45:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QfTAe-0006ZT-0Z for emacs-devel@gnu.org; Sat, 09 Jul 2011 04:45:53 -0400 Original-Received: from mailout-de.gmx.net ([213.165.64.22]:51067) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1QfTAd-0006ZG-9f for emacs-devel@gnu.org; Sat, 09 Jul 2011 04:45:51 -0400 Original-Received: (qmail invoked by alias); 09 Jul 2011 08:45:49 -0000 Original-Received: from 62-47-36-119.adsl.highway.telekom.at (EHLO [62.47.36.119]) [62.47.36.119] by mail.gmx.net (mp068) with SMTP; 09 Jul 2011 10:45:49 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX19sdHwOAPhsbBmq8Wz2SkVz7ZZa55W7VvUy8Rb7LV E7AMwB4Dc+1B78 User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 213.165.64.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:141844 Archived-At: > We may as well get rid of pop-to-buffer-same-window (those who want to > provide a LABEL can use pop-to-buffer instead). I wouldn't object. The functionality is obviously needed to get rid of all those (add-to-list 'same-window-buffer-names (purecopy "*Python*")) ;;;###autoload (add-hook 'same-window-buffer-names (purecopy "*scheme*")) but if there are any doubts about too many pop-to-buffer-... or display-buffer-... definitions please let me know. >> - For those places that intend the "act on the selected window" >> behavior---which is the minority---change the code to call >> (set-window-buffer (selected-window) buffer), instead of >> switch-to-buffer. > > Note that (set-window-buffer (selected-window) buffer) isn't quite good > enough, since set-window-buffer will be happy to change the buffer of > a mini-window, whereas callers of switch-to-buffer that want to operate > on the selected window should signal an error in that case. > I think adding a `selected-window-only' argument to switch-to-buffer is > a better solution so callers don't need to worry about such details of > set-window-buffer. What precisely would the semantics of this argument be? martin