Re: New package `outline-occur'

martin rudalics <[email protected]> writes:

> I attach a copy of what I think we could do with the sole purpose of
> understanding how to process and document it.
>
> The idea is that any buffer name or category present in what I'd call
> 'display-buffer-bound-alist' should match the buffer name or the
> category of the ACTION argument of 'display-buffer'.  Is that right?

So, with this patch, the list of action functions built by
`display-buffer' would look as follows (by order of precedence):

- `display-buffer-overriding-action' [ set by programs WITH UTMOST CARE ]
- `display-buffer-alist' [ set by users ]
- `special-action' [ depends on the `special-display-function' variable
                     and the return value of `special-display-p' for the
                     BUFFER-OR-NAME argument passed to `display-buffer' ]
- `display-buffer-bound-alist' [ introduced by this patch and let-bound ]
- ACTION argument passed to `display-buffer'
- extra-action [ depends on the FRAME argument passed to
                 `display-buffer' ]
- `display-buffer-base-action' [ set by users ]
- `display-buffer-fallback-action' [ it should never be set by programs
                                     or users ]

Thus, Elisp programs would let-bind `display-buffer-bound-alist' to set
the default behavior of `display-buffer'---as defined by the Elisp
programmer.  This way the user can still customize this behavior by
setting the `display-buffer-alist' variable.

Is that correct?

Thanks!

        Roi