unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Roland Winkler <winkler@gnu.org>,
	Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
	martin rudalics <rudalics@gmx.at>,
	"N. Jackson" <nljlistbox2@gmail.com>,
	emacs-devel@gnu.org
Subject: RE: Suggesting `frame-split-biggest-window' Re: customize location and shape of a new window in a frame
Date: Fri, 14 Sep 2018 21:58:02 -0700 (PDT)	[thread overview]
Message-ID: <953cd685-fb36-49e2-bb55-08674e2a17d0@default> (raw)
In-Reply-To: <34498.70574.322595.23452@gargle.gargle.HOWL>

> 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.

+1



  reply	other threads:[~2018-09-15  4:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 20:31 customize location and shape of a new window in a frame Roland Winkler
2018-09-11 21:22 ` Eric Abrahamsen
2018-09-12 19:36   ` N. Jackson
2018-09-12 20:12     ` Eric Abrahamsen
2018-09-12 23:21       ` Suggesting `frame-split-biggest-window' " N. Jackson
2018-09-13  7:45         ` martin rudalics
2018-09-13 13:07           ` N. Jackson
2018-09-14  8:31             ` martin rudalics
2018-09-13 16:33           ` Eric Abrahamsen
2018-09-14  8:33             ` martin rudalics
2018-09-14 16:56               ` Eric Abrahamsen
2018-09-15  8:17                 ` martin rudalics
2018-09-14  5:17           ` Roland Winkler
2018-09-14  8:33             ` martin rudalics
2018-09-14 12:01               ` Stefan Monnier
2018-09-15  4:12                 ` Roland Winkler
2018-09-15  4:58                   ` Drew Adams [this message]
2018-09-15  8:18                   ` martin rudalics
2018-09-15 16:34                     ` Roland Winkler
2018-09-15 18:34                       ` Stefan Monnier
2018-09-15 19:21                         ` Roland Winkler
2018-09-15 12:24                 ` N. Jackson
2018-09-15 14:56                   ` Stefan Monnier
2018-09-15  0:46               ` Richard Stallman
2018-09-15  8:17                 ` martin rudalics
2018-09-16  3:14                   ` Richard Stallman
2018-09-16 19:05                     ` John Yates
2018-09-16 19:22                       ` Eli Zaretskii
2018-09-16 20:30                       ` Drew Adams
2018-09-13 16:38         ` Eric Abrahamsen
2018-09-12 14:54 ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=953cd685-fb36-49e2-bb55-08674e2a17d0@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=nljlistbox2@gmail.com \
    --cc=rudalics@gmx.at \
    --cc=winkler@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).