From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19461@debbugs.gnu.org
Subject: bug#19461: 25.0.50; doc of `display-buffer-*' functions that take ALIST arg
Date: Sat, 03 Aug 2019 14:08:57 +0300 [thread overview]
Message-ID: <83lfwaecae.fsf@gnu.org> (raw)
In-Reply-To: <87imreldew.fsf@mouse.gnus.org> (message from Lars Ingebrigtsen on Sat, 03 Aug 2019 13:02:47 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, drew.adams@oracle.com,
> 19461@debbugs.gnu.org
> Date: Sat, 03 Aug 2019 13:02:47 +0200
>
> martin rudalics <rudalics@gmx.at> writes:
>
> >> 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.
>
> Perhaps the doc strings of the other functions should say so?
I think they should, yes.
> Or perhaps be renamed to --pop-up-window (etc)?
That ship has sailed, so I don't think we should/could rename those
functions.
next prev parent reply other threads:[~2019-08-03 11:08 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 [this message]
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=83lfwaecae.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19461@debbugs.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 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).