From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 19461@debbugs.gnu.org
Subject: bug#19461: 25.0.50; doc of `display-buffer-*' functions that take ALIST arg
Date: Sat, 3 Aug 2019 12:59:14 +0200 [thread overview]
Message-ID: <4afeb793-59bf-fc35-f3ed-79995c33ad30@gmx.at> (raw)
In-Reply-To: <83r262ehgi.fsf@gnu.org>
>> This problem is with us since day one of that buffer display code.
>> It's probably due to the fact that the 'display-buffer-*' functions
>> are inherently internal but never have been marked as such in order to
>> describe them in the manual and allow users to add new ones.
>
> What are the non-internal functions which should be called instead of
> these ones (and will call these ones when needed)?
There is just one and that is 'display-buffer' itself. Functions like
'display-buffer-pop-up-window' or 'display-buffer-same-window' should
never get called by anyone but 'display-buffer' or a function
(in-)directly called by 'display-buffer'. 'display-buffer' is the
only function that can handle precedences correctly and knows how to
build ALIST from its various ingredients. In fact, one can rewrite
any 'display-buffer-*' function with the help of 'display-buffer' and
an appropriate ACTION argument.
>> Saying what it is is non-trivial, see section 28.13.3 of the Elisp
>> manual. So I have no good idea how to do what you propose.
>
> I gave it a go on the master branch, please take a look.
Good! Referring to the Elisp manual seems like the only way to add
something useful.
Thanks, martin
next prev parent reply other threads:[~2019-08-03 10:59 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
2019-08-03 7:58 ` martin rudalics
2019-08-03 9:17 ` Eli Zaretskii
2019-08-03 10:59 ` martin rudalics [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4afeb793-59bf-fc35-f3ed-79995c33ad30@gmx.at \
--to=rudalics@gmx.at \
--cc=19461@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.