|
From: | Juri Linkov |
Subject: | bug#32607: 27.0.50; pop-to-buffer in next-error-no-select |
Date: | Wed, 05 Sep 2018 00:28:30 +0300 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) |
>>>> But it fails when using C-o from the already displayed *grep*. >>>> I think next-error-no-select should override the user setting with >>>> display-buffer-overriding-action because the purpose of pop-to-buffer in >>>> next-error-no-select is to ensure the *grep* buffer is displayed somewhere: >>> >>> And if a user wanted to pop up a new window here? >> >> It pops up according to user setting but only when >> this buffer is not displayed already in other window. > > Still: IMHO it's not the task of the calling function to fix a bad > user customization. What is bad in user customization? It's normal customization that corresponds to the old way of using same-window-regexps. It's not responsibility of user customization to workaround deficiencies in core functions. The task of next-error-no-select is to check if the buffer is already displayed, not to pop up a new buffer. There is no such problem in other commands that use pop-to-buffer.
[Prev in Thread] | Current Thread | [Next in Thread] |