Re: display-buffer-alist simplifications

[Chong Yidong <cyd@stupidchicken.com>]

"Drew Adams" <drew.adams@oracle.com> writes:

>> now that we've settled on a workable design
>
> You/we have?  I hadn't gotten that impression from scanning the
> thread.  I (think I) see new proposals and counter-proposals everyday.

You haven't been reading the thread carefully, then.

>> For example, I would not spend time on the defcustom definitions for
>> display-buffer-alist and display-buffer-default-rule, if that proves
>> complicated---you could just make them defvars for now.
>
> Huh?  I thought the decision was that there was no hurry for Emacs 24
> and that you wanted to get this right first.  Sounds like now someone
> wants to go to market in a hurry.
>
> I say take the time to get it right.  What's the rush?

Conversely, as long as the Emacs 23 variables continues to work, we have
all the time in the world to introduce the full set of new window
management features.

The hold-up is fine for now, because meanwhile other bugs are getting
fixed and the manuals are getting updated.  But the timeline is not
infinitely elastic---the whole point of a feature freeze is that new
features are supposed to be ready for testing/integration at more or
less the same time, instead of waiting on one another.

Another reason I would prefer to reduce the initial set of changes to
the minimum working set of "base" code is to get that code into the
repository sooner rather than later.  Then other Emacs developers can
help at working out integration issues, reducing the current bottleneck
(i.e. "Martin doing everything").