all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, 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: Sun, 4 Aug 2019 18:06:10 -0700 (PDT)	[thread overview]
Message-ID: <cdebe16d-0c1b-4169-801d-221a7dd60dc8@default> (raw)
In-Reply-To: <b6ad3d9c-ac85-a850-ed53-c8b5ce58e515@gmx.at>

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

If saying what it is is non-trivial for the
maintainers, and I'm sure you're right about
that, then imagine the difficulty of a user to
understand what it is, especially if we do not
say what it is.

If it can be said only in the manual, then the
doc string can, I guess, just punt with a link
to the appropriate section of the manual.





  parent reply	other threads:[~2019-08-05  1:06 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
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 [this message]
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=cdebe16d-0c1b-4169-801d-221a7dd60dc8@default \
    --to=drew.adams@oracle.com \
    --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 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.