Subject: Re: bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN

From: martin rudalics <[email-masked]>
Date: Fri, 08 Feb 2013 10:59:48 +0100

> It's a valid return value, but only when display-buffer is *unable to
 > display the buffer*.  It is *very* rare to be unable to do so.  E.g. it
 > will never happen unless at least one of pop-up-frame-function or
 > display-buffer-fallback-action is changed.

To make it happen you have to make all existing windows dedicated and
display some other buffer, inhibit popping up new windows, and inhibit
popping up new frames.

martin