From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : display-buffer-alist actions
Date: Thu, 25 Feb 2021 07:00:08 +0000 [thread overview]
Message-ID: <SA2PR10MB44742E6170513BAE41C53CA2F39E9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87lfbc93fe.fsf@web.de>
> > > I've read and re-read the documentation for
> > > display-buffer-alist and I cannot quite understand it.
> >
> > (You're not alone.)
> >
> > I suspect it's not just a doc problem. It's
> > the behavior that's complex.
>
> The behavior is complex since the task is. The approach is not
> unnecessarily complex in my eyes.
I agree (to the extent that I understand it).
I've said as much several times before.
It provides a comprehensive solution, which is
necessarily complex.
My complaint is that we don't also provide some
simple to use constructs for simple use cases.
In particular, I've very glad we still have
the `special-display' stuff available. Simple,
great for some simple use cases. But when the
new, comprehensive solution was created (a
_good_ thing), Emacs simultaneously deprecated
`special-display'. We _have_ it, but we're
discouraged from using it.
That deprecation I object to.
But I do appreciate that it's still supported.
I hope it will continue to be so. And I still
have hopes that the deprecation will be lifted
from it someday. Users are in general unaware
of it now (it was removed from the manual etc.),
even though it's very good for the simple use
cases it handles.
> > That leads to complicated doc, whether or not the doc is correct.
>
> At least in my (master) Emacs the docs contain a node
>
> (info "(elisp) The Zen of Buffer Display")
>
> It's quite nice and easy to understand. Must be quite new I guess.
Thanks for pointing it out. I'll take a look.
It's not that new apparently - it's in Emacs
26.3, at least.
next prev parent reply other threads:[~2021-02-25 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 17:44 display-buffer-alist actions Eric S Fraga
2021-02-24 19:52 ` Joost Kremers
2021-02-24 20:08 ` Joost Kremers
2021-02-24 21:08 ` TRS-80
2021-02-24 20:57 ` Michael Heerdegen
2021-02-25 16:25 ` Eric S Fraga
2021-02-25 20:40 ` Garjola Dindi
2021-02-24 21:15 ` Stefan Monnier
2021-02-25 16:34 ` Eric S Fraga
2021-02-25 16:51 ` Stefan Monnier
2021-02-26 9:43 ` Eric S Fraga
2021-02-25 0:00 ` [External] : " Drew Adams
2021-02-25 4:28 ` Michael Heerdegen
2021-02-25 7:00 ` Drew Adams [this message]
2021-02-25 14:26 ` Stefan Monnier
2021-02-25 16:22 ` Drew Adams
2021-02-25 16:36 ` Eric S Fraga
2021-02-25 16:27 ` Eric S Fraga
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=SA2PR10MB44742E6170513BAE41C53CA2F39E9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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.
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).