bug#81512: [PATCH] Add command `outline-occur'

Juri Linkov <[email protected]> writes:

>>>  > Maybe by naming it as internal: display-buffer--alist?
>>>  > Or if it's too confusing, then maybe display-buffer-internal-alist?
>>>
>>> But we want to advertise it in the manual and we usually don't do that
>>> for internal variables.
>>
>> What about `display-buffer-program-alist'?  I think it makes it clear
>> that it is intended to be used from Elisp code.
>
> Or maybe simply `display-buffer-prog-alist' like in `prog-mode'.
> (However, this is related to modes for program languages.)
> Another variant is `display-buffer-override-alist'.

The problem I see with the name `display-buffer-override-alist' is that
while `display-buffer-overriding-action' has the highest priority and
overrides all other variables, `display-buffer-alist' would be processed
before `display-buffer-override-alist', so the latter would not override
the former.  It also feels a bit confusing to have both
`display-buffer-overriding-action' and `display-buffer-override-alist'.

I'm adding the order of priority below for reference:

- The variable `display-buffer-overriding-action'.
- The user option `display-buffer-alist'.
- The variable `display-buffer-internal-alist'.
- The ACTION argument.
- The user option `display-buffer-base-action'.
- The constant `display-buffer-fallback-action'.

        Roi