From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 26233@debbugs.gnu.org
Subject: bug#26233: 26.0.50; [PATCH] Improve documentation for display-buffer-alist
Date: Sat, 25 Mar 2017 09:00:02 +0100 [thread overview]
Message-ID: <874lyh6b25.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <58D56B7A.2080909@gmx.at> (martin rudalics's message of "Fri, 24 Mar 2017 19:54:50 +0100")
On 2017-03-24, at 19:54, martin rudalics wrote:
>> in Bug#25946 we discussed how to replace the obsolete variables
>> special-display-buffer-names and special-display-regexps. The
>> attached patch extends the doc string of display-buffer-alist based
>> on that discussion.
>
> 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.
Best wishes
Jens
next prev parent reply other threads:[~2017-03-25 8:00 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 [this message]
2017-03-25 9:28 ` martin rudalics
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=874lyh6b25.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=lechten@wi.uni-muenster.de \
--cc=26233@debbugs.gnu.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).