From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.devel Subject: Re: display-buffer-function obsolete since 24.3 Date: Wed, 06 Feb 2013 21:08:51 +0100 Message-ID: <87mwvh5hnw.fsf@web.de> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1360181240 17655 80.91.229.3 (6 Feb 2013 20:07:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 6 Feb 2013 20:07:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 06 21:07:41 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 1U3BHQ-0005hA-2E for ged-emacs-devel@m.gmane.org; Wed, 06 Feb 2013 21:07:40 +0100 Original-Received: from localhost ([::1]:42256 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3BH7-0001Ro-8L for ged-emacs-devel@m.gmane.org; Wed, 06 Feb 2013 15:07:21 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:40868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3BH4-0001Rb-7r for emacs-devel@gnu.org; Wed, 06 Feb 2013 15:07:19 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U3BH2-0007Bd-ST for emacs-devel@gnu.org; Wed, 06 Feb 2013 15:07:18 -0500 Original-Received: from mout.web.de ([212.227.17.11]:51839) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U3BH2-00079p-IK for emacs-devel@gnu.org; Wed, 06 Feb 2013 15:07:16 -0500 Original-Received: from drachen.dragon ([92.74.177.220]) by smtp.web.de (mrweb002) with ESMTPA (Nemesis) id 0LjJaZ-1UfGaC0yhr-00d0qo; Wed, 06 Feb 2013 21:07:15 +0100 Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: (Leo Liu's message of "Thu, 31 Jan 2013 19:47:39 +0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) X-Provags-ID: V02:K0:BK0iSOgPH7nN1yQImb9AHqGBQyehM+jw3r+plv1DOpd AEhQqQgRM4Sum1NB4Mqs7akx0dA7QGL0QxoYhjt8oBzMhp8OzU lHhMl3HTyxrpFWlrMM6KVJCjWi/27BFRHm2JoSsruxqVh7l9dm Fc05n60zPN8QmIUY4zk9ojpHkxSBSYx7pf7wVlBfv/RPzzjtrN qd6mHxZaq2F4RoT+U23apPTgz5YXZs1PcDOLvealss= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.11 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:156841 Archived-At: Leo Liu writes: > Hi there, > > Before we have a single entry to control display-buffer now it seems it > has become complicated: > > display-buffer-overriding-action > display-buffer-alist > display-buffer-base-action > display-buffer-fallback-action > > Does this complexity offer a superset of display-buffer-function? Maybe calling it a superset would be too much, since you can do everything possible with elisp with `display-buffer-function'. The point is that you can IMO do most common stuff more easily. Did you read (elisp) Display Action Functions? It's worth reading and trying to understand, although it's indeed quite complex and abstract. Using `display-buffer-alist' is quite comfortable once you got used to it. Regards, Michael.