From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: RE: Documenting buffer display
Date: Sat, 20 Oct 2018 08:22:11 -0700 (PDT) [thread overview]
Message-ID: <969a77ef-233b-428f-bf08-dba31d7cb895@default> (raw)
In-Reply-To: <5BCB1D82.3020108@gmx.at>
> Attached find a rewrite of the documentation of buffer display
> functions to be applied against the release branch.
>
> Work in progress. Proofreading and suggestions welcome.
>
> Thanks for the attention, martin
Thanks very much for working on this area of the documentation!
This is an area where things have become more complicated and
could use clarification. Working on this really helps.
I only skimmed your patch, but I have at least this comment: I
object to the removal of doc for, and the downplay of support
for, `pop-up-frames' etc. Such variables are very handy; they
should continue to be fully supported and even touted, IMO.
Yes, I am perhaps a lone voice in this regard, but I wanted
to once again voice my disagreement about this, FWIW.
In addition to the wholesale removal of such doc, this, for
instance, is the wrong direction to take, IMHO:
+Many efforts in the design of @code{display-buffer} have been given
+to maintain compatibility with code that uses older options like
+@code{pop-up-windows}, @code{pop-up-frames},
+@code{pop-up-frame-alist}, @code{same-window-buffer-names} and
+@code{same-window-regexps}. Applications and users should refrain
+from using these options in future code. Above we already warned
+against customizing @code{pop-up-frame-alist}. Here we describe how
+to convert the remaining options to use display actions instead.
(I don't object to the "many efforts...to maintain compatibility...".
In fact, I applaud such effort and compatibility. I object to it being
considered only backward compatibility. I object to discouraging
or phasing out such useful constructs. If they didn't exist then
we should want to invent them...)
Being able to simply bind an option such as `pop-up-frames',
to change the behavior of existing code, is very useful.
Richard's arguments why dynamic binding of variables (in _addition_
to lexical binding) is particularly useful for _Emacs_ is relevant here.
It is as relevant today as when it was written, decades ago:
https://www.gnu.org/software/emacs/emacs-paper.html#SEC17
https://www.gnu.org/software/emacs/emacs-paper.html#SEC18
Please keep supporting, and not at all discourage, `pop-up-frames'
and similar.
Thanks for listening, and thanks for the ton of careful work you've
put in for this documentation and to make buffer display more
configurable.
next prev parent reply other threads:[~2018-10-20 15:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 12:20 Documenting buffer display martin rudalics
2018-10-20 13:21 ` Eli Zaretskii
2018-10-20 18:02 ` martin rudalics
2018-10-21 12:56 ` Eli Zaretskii
2018-10-22 9:06 ` martin rudalics
2018-10-22 13:55 ` Eli Zaretskii
2018-10-22 19:14 ` martin rudalics
2018-10-22 19:27 ` Eli Zaretskii
2018-10-23 8:58 ` martin rudalics
2018-10-23 11:26 ` Pierre-Yves Luyten
2018-10-23 13:45 ` martin rudalics
2018-10-23 17:40 ` Stefan Monnier
2018-10-23 14:04 ` Drew Adams
2018-10-23 18:18 ` martin rudalics
2018-10-23 15:18 ` Eli Zaretskii
2018-10-23 18:23 ` martin rudalics
2018-10-23 19:07 ` Eli Zaretskii
2018-10-24 9:44 ` martin rudalics
2018-10-24 14:48 ` Eli Zaretskii
2018-10-24 17:40 ` martin rudalics
2018-10-24 18:25 ` Eli Zaretskii
2018-10-25 20:42 ` Juri Linkov
2018-10-23 15:52 ` Alan Mackenzie
2018-10-23 18:25 ` martin rudalics
2018-11-08 19:25 ` martin rudalics
2018-10-22 1:39 ` Michael Welsh Duggan
2018-10-22 5:54 ` Eli Zaretskii
2018-10-20 15:22 ` Drew Adams [this message]
2018-10-20 18:02 ` martin rudalics
2018-10-20 18:24 ` Drew Adams
2018-10-21 8:22 ` martin rudalics
2018-11-04 9:06 ` 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=969a77ef-233b-428f-bf08-dba31d7cb895@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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 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.