From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19461@debbugs.gnu.org
Subject: bug#19461: 25.0.50; doc of `display-buffer-*' functions that take ALIST arg
Date: Fri, 02 Aug 2019 22:44:43 +0200 [thread overview]
Message-ID: <8736ijmh50.fsf@mouse.gnus.org> (raw)
In-Reply-To: <97135b13-1c29-44a9-bfd9-f12966e56cd4@default> (Drew Adams's message of "Sun, 28 Dec 2014 12:50:04 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> The doc strings say nothing about parameter ALIST, which in many cases
> is the most important parameter.
>
> One can guess that it is an alist. And one can guess, for the doc
> strings that mention `inhibit-switch-frame' or
> `pop-up-frame-parameters', that one or more of its entries can have such
> a key, but that's all. No guessing helps for
> `display-buffer-(below-selected|at-bottom|in-previous-window|
> use-some-window|no-window|same-window|assq-regexp)'. Likewise, some of
> the "internal" functions.
It is indeed pretty obscure what ALIST is. Some of the functions say
things like
---
If ALIST contains a ’window-min-height’ entry, this function
ensures that the window used is or can become at least as high as
specified by that entry’s value.
---
but looking at the code, it passes ALIST around a lot. So is ALIST a
general buffer/window property thing? At least one of these doc strings
should say what it is, and the rest could refer to it.
I've Cc'd Martin.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-02 20:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 20:50 bug#19461: 25.0.50; doc of `display-buffer-*' functions that take ALIST arg Drew Adams
2019-08-02 20:44 ` Lars Ingebrigtsen [this message]
2019-08-03 7:58 ` martin rudalics
2019-08-03 9:17 ` Eli Zaretskii
2019-08-03 10:59 ` martin rudalics
2019-08-03 11:02 ` Lars Ingebrigtsen
2019-08-03 11:08 ` Eli Zaretskii
2019-08-04 2:45 ` Michael Heerdegen
2019-08-04 8:01 ` martin rudalics
2019-08-04 11:18 ` Michael Heerdegen
2019-08-05 9:22 ` martin rudalics
2019-08-04 11:48 ` Lars Ingebrigtsen
2019-08-04 12:13 ` Michael Heerdegen
2019-08-04 15:39 ` Eli Zaretskii
2019-08-05 9:23 ` martin rudalics
2021-09-25 16:12 ` Stefan Kangas
2021-09-26 9:11 ` martin rudalics
2021-09-26 9:34 ` Stefan Kangas
2019-08-05 1:06 ` Drew Adams
2019-08-05 9:23 ` martin rudalics
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=8736ijmh50.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=19461@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).