From: martin rudalics <rudalics@gmx.at>
To: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
Cc: 26233@debbugs.gnu.org
Subject: bug#26233: 26.0.50; [PATCH] Improve documentation for display-buffer-alist
Date: Sat, 25 Mar 2017 10:28:39 +0100 [thread overview]
Message-ID: <58D63847.1060906@gmx.at> (raw)
In-Reply-To: <874lyh6b25.fsf@informationelle-selbstbestimmung-im-internet.de>
>> Thanks. Personally I'd prefer having that in the Elisp manual. Either
>> in a new subsection or at the end of section 27.14 Action Functions for
>> `display-buffer'? Code in doc-strings is sometimes tedious to read.
>
> I'm surprised. I consider that information relevant to ordinary
> users, not only developers. As pointed out by Drew Adams, probably
> a new section in the Emacs manual is necessary. Also, she convinced
> me that much more information is necessary, which I'm unable to
> provide.
That's why I used the term "personally". If you think that putting
the information in the doc-string is better, let's do that.
martin
next prev parent reply other threads:[~2017-03-25 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 13:25 bug#26233: 26.0.50; [PATCH] Improve documentation for display-buffer-alist Jens Lechtenboerger
2017-03-24 14:51 ` Drew Adams
2017-03-25 7:53 ` Jens Lechtenboerger
2017-03-25 8:32 ` Eli Zaretskii
2017-03-25 14:58 ` Jens Lechtenboerger
2017-03-25 15:57 ` Eli Zaretskii
2017-03-25 17:14 ` Jens Lechtenboerger
[not found] ` <<878tnt6bdi.fsf@informationelle-selbstbestimmung-im-internet.de>
[not found] ` <<83shm1bvud.fsf@gnu.org>
2017-03-25 14:36 ` Drew Adams
2017-03-26 8:38 ` martin rudalics
2017-03-26 14:17 ` Eli Zaretskii
2017-03-26 17:45 ` Drew Adams
2017-03-24 18:54 ` martin rudalics
2017-03-25 8:00 ` Jens Lechtenboerger
2017-03-25 9:28 ` martin rudalics [this message]
2019-06-24 16:54 ` Lars Ingebrigtsen
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=58D63847.1060906@gmx.at \
--to=rudalics@gmx.at \
--cc=26233@debbugs.gnu.org \
--cc=lechten@wi.uni-muenster.de \
/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).