Re: Does display-buffer display the buffer or not?

[martin rudalics]

>> That's a correct conclusion, indeed.  The "creating a new frame" part
>> would then have to sidestep `pop-up-frame-function', obviously.
>
> So the average programmers is supposed to know how to handle this, but
> those writing for example the routines that shows a backtrace when
> there is an error are not.
>
> Why is the average programmer better at avoiding looping here?

Emacs doesn't pop up the *Backtrace* buffer by default so the "average"
user is not affected.  And the average user is not supposed to customize
`pop-up-frame-function' either.  I intended this as a hint for people
writing, for example, a silly `pop-up-frame-function' so they can find
the cuplrit easier.  And, obviously, if a function is allowed to return
nil, the doc-string of the function should say so.

martin