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: The window-pub branch Date: Sun, 21 Nov 2010 18:51:00 +0100 Message-ID: <4CE95C04.1090905@gmx.at> References: 4CE031A6.8010403@gmx.at <4CE56872.6050502@gmx.de> <4CE57519.7030403@gmx.at> <4CE59AC2.9030201@gmx.de> <4CE62E91.4030501@gmx.at> <4CE67DC5.7020603@gmx.de> <4CE68D34.1040308@gmx.at> <4CE6A9C3.5060400@gmx.de> <4CE792B7.7090406@gmx.at> <4CE7DEAB.8030401@gmx.de> <4CE80D77.10801@gmx.at> <4CE83A6B.6090904@gmx.de> <4CE8EB28.3060607@gmx.at> <4CE91FED.9060705@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1290361879 19336 80.91.229.12 (21 Nov 2010 17:51:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 21 Nov 2010 17:51:19 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 21 18:51:13 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PKE4G-0004tR-BS for ged-emacs-devel@m.gmane.org; Sun, 21 Nov 2010 18:51:12 +0100 Original-Received: from localhost ([127.0.0.1]:45635 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PKE4F-0004gB-BH for ged-emacs-devel@m.gmane.org; Sun, 21 Nov 2010 12:51:11 -0500 Original-Received: from [140.186.70.92] (port=51335 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PKE49-0004ft-SW for emacs-devel@gnu.org; Sun, 21 Nov 2010 12:51:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PKE48-0005Py-8l for emacs-devel@gnu.org; Sun, 21 Nov 2010 12:51:05 -0500 Original-Received: from mailout-de.gmx.net ([213.165.64.23]:41150 helo=mail.gmx.net) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1PKE47-0005Ph-Qf for emacs-devel@gnu.org; Sun, 21 Nov 2010 12:51:04 -0500 Original-Received: (qmail invoked by alias); 21 Nov 2010 17:51:01 -0000 Original-Received: from 62-47-42-158.adsl.highway.telekom.at (EHLO [62.47.42.158]) [62.47.42.158] by mail.gmx.net (mp015) with SMTP; 21 Nov 2010 18:51:01 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX18GXjgkaOMG1n98FFL/QQiXncJwQJVNmXMgPIdTuD 2gIhlR3jxNBsKb User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <4CE91FED.9060705@gmx.de> X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:132972 Archived-At: > However there are some pre-configured entries with specifiers > in `display-buffer-names'. > > You have already pre-configured entries in `display-buffer-regexps' Yes. But these are not tied to applications. They just mimic the old default values of `pop-up-windows' etc. I can't put application specific things in `display-buffer-names'. We could have done that long ago, for example for info or help, instead of clobbering options like `same-window-buffer-names' via add-hook. It doesn't help putting them there for the following simple reason: (1) The user customizes `display-buffer-names' and saves the customizations to his .emacs. (2) An application wants to change a preconfigured value or introduce a new one. In this case you would have to merge the preconfigured value with the one on .emacs. I can neither expect the user to do this manually nor write a program in reasonable time that solves the possible conflicts in this area. Preconfigured, application dependent values must not reside in `display-buffer-names'. That's why I'd need a shadow variable to implement your propsal. >> Would your really allow "other packages" mess with user options? > > Yes, sure. As long as it's done safely via an helper-function that > you wrote. For example: > > (display-add-buffer-names-default-entry '((foo-normal)