From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: cyd@gnu.org, emacs-devel@gnu.org
Subject: Re: Marking old window variables obsolete
Date: Thu, 09 Aug 2012 19:01:22 +0300 [thread overview]
Message-ID: <83r4rgdpgt.fsf@gnu.org> (raw)
In-Reply-To: <6863B68E762149B28EF9C1A159D441A3@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Thu, 9 Aug 2012 07:12:57 -0700
>
> > The new display-buffer machinery still supports the following
> > variables:
> >
> > special-display-buffer-names
> > special-display-regexps
> > special-display-frame-alist
> > special-display-function
> > same-window-buffer-names
> > same-window-regexps
> > display-buffer-reuse-frames
> >
> > I think we can mark these as obsolete for 24.2. Any objections?
> >
> > There's also pop-up-frames and pop-up-windows, but I think we
> > can wait a few releases before marking those as obsolete.
>
> FWIW and for the record, I disagree with _all_ of that proposal. Please do not
> do this. There should be _no_ hurry to do anything of the sort. Why can't you
> wait a few releases - or more - for all of the above?
Deprecation does not mean removal. I'm sure you know that.
next prev parent reply other threads:[~2012-08-09 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 9:43 Marking old window variables obsolete Chong Yidong
2012-08-09 14:12 ` Drew Adams
2012-08-09 16:01 ` Eli Zaretskii [this message]
2012-08-09 16:10 ` Drew Adams
2012-08-09 16:53 ` Eli Zaretskii
2012-08-09 18:16 ` Drew Adams
2012-08-09 18:37 ` Óscar Fuentes
2012-08-09 21:51 ` Drew Adams
2012-08-09 19:28 ` Eli Zaretskii
2012-08-09 21:53 ` Drew Adams
2012-08-10 6:18 ` Eli Zaretskii
2012-08-09 14:53 ` Stefan Monnier
2012-08-09 15:57 ` Eli Zaretskii
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=83r4rgdpgt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).