[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32607: 27.0.50; pop-to-buffer in next-error-no-select
From: |
martin rudalics |
Subject: |
bug#32607: 27.0.50; pop-to-buffer in next-error-no-select |
Date: |
Sun, 02 Sep 2018 09:14:22 +0200 |
> Suppose we have such customization:
>
> (setq display-buffer-alist '(("\\`\\*grep\\*\\'"
display-buffer-same-window)))
>
> Now after running grep with a non-empty output in ‘emacs -Q’,
> typing ‘C-o’ (compilation-display-error) will display two identical
> buffers instead of displaying the buffer with the found grep hit.
>
> The problem is with pop-to-buffer in next-error-no-select.
> I wonder what is an idiomatic way to ensure a buffer is already
> displayed in some window, to not display the same buffer
> in other window?
I'm not quite sure I understand: Is there a reason you did not supply
'display-buffer-reuse-window' in the above customization?
martin
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/01
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select,
martin rudalics <=
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/02
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, martin rudalics, 2018/09/03
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/03
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, martin rudalics, 2018/09/04
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/04
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, martin rudalics, 2018/09/05
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/05
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, martin rudalics, 2018/09/06
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Juri Linkov, 2018/09/06
- bug#32607: 27.0.50; pop-to-buffer in next-error-no-select, Eli Zaretskii, 2018/09/07