[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWI
From: |
martin rudalics |
Subject: |
bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN |
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
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, (continued)
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Juri Linkov, 2013/02/08
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Stefan Monnier, 2013/02/08
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, martin rudalics, 2013/02/09
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Juri Linkov, 2013/02/10
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, martin rudalics, 2013/02/10
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Juri Linkov, 2013/02/11
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, martin rudalics, 2013/02/11
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Leo Liu, 2013/02/11
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Leo Liu, 2013/02/14
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN, Stefan Monnier, 2013/02/14
- bug#13594: 24.2.92; [PATCH] compilation-start doesn't consider nil OUTWIN,
martin rudalics <=