[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32825: 27.0.50; Deterministic window management
From: |
Juri Linkov |
Subject: |
bug#32825: 27.0.50; Deterministic window management |
Date: |
Thu, 08 Nov 2018 23:58:20 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) |
>> I only added display-buffer-below-selected to pop-to-buffer
>> of "*Backtrace*" after display-buffer-in-previous-window,
>> and in `emacs -Q` with 3 windows where the bottom window is
>> very low, subsequent errors are displayed in different windows.
>
> Like this
>
> (pop-to-buffer
> debugger-buffer
> `((display-buffer-reuse-window
> display-buffer-in-previous-window
> display-buffer-below-selected)
> . (,(when (and (window-live-p debugger-previous-window)
> (frame-visible-p
> (window-frame debugger-previous-window)))
> `(previous-window . ,debugger-previous-window)))))
Exactly.
> I presume. This will, in the first invocation, make a new window below
> the selected one or reuse such a window because there is no previous
> window. Later on, that window gets reused here as expected,
> regardless of whether the frame is wide or not. With emacs -Q, at
> least. Maybe you have additional customizations or changes at work?
With emacs -Q and without additional customizations, every error
(e.g. evaluating a non-existent variable) is shown in a different window
(first in 1, then in 2, then again in 1):
+---------------------+
| 1. |
| |
+---------------------+
| 2. |
| |
+---------------------+
| low selected window |
+---------------------+
This bug can be avoided by adding display-buffer-at-bottom
after display-buffer-below-selected, i.e. by using such actions:
display-buffer-reuse-window
display-buffer-in-previous-window
display-buffer-below-selected
display-buffer-at-bottom
This provides a nicer behavior because display-buffer-at-bottom tries
to resize other windows to accommodate the *Backtrace*.
- bug#32825: 27.0.50; Deterministic window management, (continued)
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/03
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/04
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/04
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/05
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/05
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/06
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/06
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/07
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/07
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/08
- bug#32825: 27.0.50; Deterministic window management,
Juri Linkov <=
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/09
- bug#32825: 27.0.50; Deterministic window management, Michael Heerdegen, 2018/11/09
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/09
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/10
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/11
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/11
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/12
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/12
- bug#32825: 27.0.50; Deterministic window management, Juri Linkov, 2018/11/12
- bug#32825: 27.0.50; Deterministic window management, martin rudalics, 2018/11/13