From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Pretest begins end-June Date: Wed, 01 Jun 2011 16:43:39 -0300 Message-ID: References: <87y61ojhp4.fsf@stupidchicken.com> <4DE60326.8040505@gmx.at> <4DE64788.5060304@gmx.at> <4DE661A8.7010706@gmx.at> <4DE68E0E.5030909@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1306957454 15447 80.91.229.12 (1 Jun 2011 19:44:14 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 1 Jun 2011 19:44:14 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 01 21:44:09 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 1QRrKp-0001jK-9y for ged-emacs-devel@m.gmane.org; Wed, 01 Jun 2011 21:44:07 +0200 Original-Received: from localhost ([::1]:39241 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRrKo-0007CE-AE for ged-emacs-devel@m.gmane.org; Wed, 01 Jun 2011 15:44:06 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRrKV-0007Br-4Y for emacs-devel@gnu.org; Wed, 01 Jun 2011 15:43:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRrKS-0001FW-Ty for emacs-devel@gnu.org; Wed, 01 Jun 2011 15:43:46 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:52693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRrKS-0001FP-FK for emacs-devel@gnu.org; Wed, 01 Jun 2011 15:43:44 -0400 Original-Received: from 121-249-126-200.fibertel.com.ar ([200.126.249.121]:12327 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QRrKR-00080T-7r; Wed, 01 Jun 2011 15:43:43 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id EF4A9660DD; Wed, 1 Jun 2011 16:43:39 -0300 (ART) In-Reply-To: <4DE68E0E.5030909@gmx.at> (martin rudalics's message of "Wed, 01 Jun 2011 21:07:58 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:140033 Archived-At: >> Let me put the question differently: >> *how* can we support code that rebinds pop-up-frames? > It's a bit like having the cake and eating it too. Yup. >> Case 1 is easy (set the default value to `unset' and you're done). > I'm not 100% sure whether this could lead to difficulties (IIUC I would Neither am I, but we know that doing nothing will also lead to difficulties. >> Case 3 doesn't sound too hard; IIUC it involves losing some >> functionality but that functionality is absent from Emacs-23 anyway. >> Do we really need to solve case 2? Probably not. > Suppose a user has set `split-height-threshold' to some value for use in > Emacs 23 and in Emacs 24 wants to use a new functionality of > `display-buffer-alist' say apply `fit-window-to-buffer' for adjusting > the window height. What shall `display-buffer' do? Respect the value > of `split-height-threshold'? Adjust the height of the window? Do both? fir-window-to-buffer is unlikely to be something that you want to apply to *all* cases, so if set it should take precedence over split-height-threshold which is meant as a default behavior. > I think I won't have great problems providing an acceptable heuristic > for `pop-up-frames'. But I'm afraid that packages outside Emacs have > some very unknown cases in store for me. As I said: not doing anything is guaranteed to bring us problems, so even if the heuristic doesn't solve all cases, it should not be too hard to come up with one that solves more problems than it introduces. Stefan