unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: martin rudalics <rudalics@gmx.at>
Cc: larsi@gnus.org, 19461@debbugs.gnu.org
Subject: bug#19461: 25.0.50; doc of `display-buffer-*' functions that take ALIST arg
Date: Sun, 04 Aug 2019 04:45:17 +0200	[thread overview]
Message-ID: <87v9vdejia.fsf@web.de> (raw)
In-Reply-To: <4afeb793-59bf-fc35-f3ed-79995c33ad30@gmx.at> (martin rudalics's message of "Sat, 3 Aug 2019 12:59:14 +0200")

martin rudalics <rudalics@gmx.at> writes:

> 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

I think the docstrings must tell that.  Because the names suggest the
opposite.  Something like "this function is for internal use only - it
is valid as an action function in the ALIST argument of
display-buffer...don't call it directly" or so?

Problematic in this regard is that there _are_ other functions like that
that are not internal AFAIK - `pop-to-buffer' for example.  How can one
distinguish them?

Michael.





  parent reply	other threads:[~2019-08-04  2:45 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
2019-08-03 11:02         ` Lars Ingebrigtsen
2019-08-03 11:08           ` Eli Zaretskii
2019-08-04  2:45         ` Michael Heerdegen [this message]
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=87v9vdejia.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=19461@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rudalics@gmx.at \
    /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).