|
From: | martin rudalics |
Subject: | bug#32607: 27.0.50; pop-to-buffer in next-error-no-select |
Date: | Wed, 05 Sep 2018 09:47:39 +0200 |
> What is bad in user customization? That this particular one (setq display-buffer-alist '(("\\`\\*grep\\*\\'" display-buffer-same-window))) apparently doesn't do what its writer intended. This customization means that its writer requests to display the buffer in the selected window _regardless_ of whether the displayed buffer is already displayed anywhere else. Such a request is legitimate (think of the case where I am perviewing a part of a buffer in another window and I do not want to change that window's point) and an application should not override it. I think the intended customization in the case at hand is (setq display-buffer-alist '(("\\`\\*grep\\*\\'" (display-buffer-reuse-window display-buffer-same-window)))) Or what am I missing? martin
[Prev in Thread] | Current Thread | [Next in Thread] |