Re: display-buffer-alist simplifications

[Juri Linkov]

> So you're suggesting I extend my scheme from
>
>    display-buffer-alist ::= list of (CONDITION . RULE)
>    RULE                 ::= (FUNCTION . ALIST)
> to
>    display-buffer-alist ::= list of (CONDITION . RULE)
>    RULE                 ::= (FUNCTIONS . ALIST)
>    FUNCTIONS            ::= list of FUNCTION
>
> so you'd run it as (run-hook-with-args-until-success FUNCTION BUFFER ALIST)?
> And we could accept a single function for FUNCTIONS (i.e. allow both of
> the above forms).
>
> That's still fairly simple and clean, so I'm OK with it, although
> it may impact the choice of predefined functions we provide in a way
> that will make it more complicated for the user to setup (rather than
> just display-buffer-same-window, she may have to choose a list of
> functions, specifying explicitly what to do when same-window doesn't
> work).
>
> But I guess it would let us form both FUNCTIONS and ALIST by
> concatenating the various FUNCTIONS and ALIST provided by the default,
> the caller, the user, and any potential override.

I think it would be good to implement this powerful and flexible scheme
(modulo terminology :)