Re: display-buffer-overriding-action

[Chong Yidong]

Chong Yidong <address@hidden> writes:

> Your rationale for not using the ACTION argument is to allow a third
> case, wherein the Lisp caller wants to specify some behavior that can
> be overridden by the user.  I contend that Lisp callers should almost
> never do that: as far as possible, they should use a `bare'
> display-buffer or pop-to-buffer call.

I should add that it is still possible to handle the "third case" by
doing

(let ((display-buffer-default-action
       (frobify display-buffer-default-action)))
  (display-buffer buffer))

This also has the advantage that the caller can do more complex
processing of the actions, such as selectively removing entries from the
function list or argument alist.  But such uses ought to be rare.