From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>,
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: Sun, 26 Mar 2017 10:38:25 +0200 [thread overview]
Message-ID: <58D77E01.6000105@gmx.at> (raw)
In-Reply-To: <f3c3d248-6836-40c8-8c34-862eb50d9817@default>
> 2. I _did_ object at the time.
Sorry, but the time was 2011 and at that time I wrote ...
Your approach will divide Emacs users into two groups: A wide majority
that continues to use the old options and a small minority able to write
their own alist based functions.
... and ...
Most of what you propose above is easily available in Emacs 23 via
`special-display-regexps'. An application would just temporarily add
the buffer, the function, and the alist to the head of that and get the
behavior without setting any arguments. Is it really worth inventing a
new `display-buffer' in order to resolve such cosmetic issues?
You did not bother to participate in that discussion and so you did not
object at the time.
> `display-buffer-alist' is notoriously difficult to
> understand and make use of. As one example, though I've
> asked several times how to use it to get the same effect
> provided by these options I've never gotten a response.
>
> That's the first step for Emacs to take, IMO, after
> undeprecating these options (as well as anything else
> "special-display", of course, such as
> `special-display-alist'): State in the doc exactly how
> they correspond to a special case of using
> `display-buffer-alist'. _Show_ the equivalence.
Despite the fact that many years ago I moved these options and the
corresponding functions from C to Elisp, I still don't understand them
and very likely never will. If you asked me how to obtain a specific
behavior with ‘display-buffer-alist’, I might be able to come up with an
answer. In any case I deeply regret that I ever got involved in this.
martin
next prev parent reply other threads:[~2017-03-26 8:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58D77E01.6000105@gmx.at \
--to=rudalics@gmx.at \
--cc=26233@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@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 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.