unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 15649@debbugs.gnu.org
Subject: bug#15649: 24.3.50; removal of "special-display" from Emacs and Elisp manuals
Date: Fri, 18 Oct 2013 15:04:47 -0700 (PDT)	[thread overview]
Message-ID: <f0288987-8740-4123-a7f9-3bc5d15e855d@default> (raw)

Please put back the doc about special-display buffers.  This is a useful
concept, and the special-display variables and functions are easy to use.

This should not have been jettisoned in your excitement to revamp
`display-buffer' and implement `display-buffer-alist'.  It is much
easier and more understandable for someone to use
`special-display-regexps' or `special-display-buffer-names' than it is
to use `display-buffer-alist' to try to accomplish the same thing.

Having `display-buffer-alist', to be able to deal with every fantastic
combination imaginable, does not preclude also having the easy-to-use
special-display features.  You've added to the possible, unintelligible,
and corner cases, but you have thrown out the baby with the bathwater:
The common, simple cases are now as complex as any others.  Nothing is
gained by throwing special-display away.  KISS.  Think of Emacs users.

In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-10-09 on LEG570
Bzr revision: 114596 jan.h.d@swipnet.se-20131009185014-vynfyw4o8p5fge54
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'





             reply	other threads:[~2013-10-18 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 22:04 Drew Adams [this message]
2013-10-21  0:55 ` bug#15649: 24.3.50; removal of "special-display" from Emacs and Elisp manuals Glenn Morris
2013-10-21  2:50   ` Drew Adams

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=f0288987-8740-4123-a7f9-3bc5d15e855d@default \
    --to=drew.adams@oracle.com \
    --cc=15649@debbugs.gnu.org \
    /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).