From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Roland Winkler" Newsgroups: gmane.emacs.devel Subject: Re: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame Date: Fri, 14 Sep 2018 23:12:50 -0500 Message-ID: <34498.70574.322595.23452@gargle.gargle.HOWL> References: <9755.9843.306611.23448@gargle.gargle.HOWL> <87y3c7pw4w.fsf@ericabrahamsen.net> <87h8iuik3g.fsf@moondust.localdomain> <87o9d2eaql.fsf@ericabrahamsen.net> <875zzawbd6.fsf_-_@moondust.localdomain> <5B9A1599.2060800@gmx.at> <17488.90794.824863.23451@gargle.gargle.HOWL> <5B9B725F.504@gmx.at> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1536984691 27570 195.159.176.226 (15 Sep 2018 04:11:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 15 Sep 2018 04:11:31 +0000 (UTC) Cc: Eric Abrahamsen , martin rudalics , emacs-devel@gnu.org, "N. Jackson" To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Sep 15 06:11:26 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g11vY-000721-UU for ged-emacs-devel@m.gmane.org; Sat, 15 Sep 2018 06:11:25 +0200 Original-Received: from localhost ([::1]:54270 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g11xf-0000cC-6A for ged-emacs-devel@m.gmane.org; Sat, 15 Sep 2018 00:13:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36321) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g11wz-0000c6-Ol for emacs-devel@gnu.org; Sat, 15 Sep 2018 00:12:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g11wz-0000kN-3i for emacs-devel@gnu.org; Sat, 15 Sep 2018 00:12:53 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35797) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g11wy-0000kA-Vy; Sat, 15 Sep 2018 00:12:53 -0400 Original-Received: from [2602:30a:2e52:d720:65b7:1416:12e7:8bfb] (port=33946 helo=regnitz) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1g11wy-00031q-OR; Sat, 15 Sep 2018 00:12:52 -0400 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:229802 Archived-At: On Fri Sep 14 2018 Stefan Monnier wrote: > > The purpose of 'display-buffer-alist' is to set up a window for one > > single buffer. It already fails miserably to make sure that two > > buffers get displayed simultaneously as the thread of Bug#32607 shows. > > Exactly. So for the purpose of "orderly setting up and saving > compositions of windows", it's of no use, but in the specific case > of BBDB (which just needs to (temporarily) pop up a single > buffer), it should be sufficient. The current discussion of 'display-buffer-alist' in the elisp manual appears rather technical, suited only for expert users. On the other hand, the variable is declared with defcustom, as if individual users should customize it to their personal liking. Phrased differently: a package like BBDB should not hijack this variable for its needs (but at best it could contribute to its value via a user option), correct? If that's the case, then it would really help to extend the documentation for this variable, stating not only that it works only for a single buffer, but also adding one or two real-world examples similar to what we have been discussing here. I believe it is quite common that users may want to customize how emacs pops up new windows. Having a unified customization scheme for that would be much nicer than having different approaches implemented in different packages.