|
From: | Dmitry Gutov |
Subject: | bug#28864: 25.3.50; next-error-no-select does select |
Date: | Sun, 29 Oct 2017 01:42:23 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Thunderbird/56.0 |
On 10/28/17 11:54 PM, Juri Linkov wrote:
Please don't remove next-error-last-buffer from change-log-mode. Actually it is legitimate use according to the documentation of next-error-last-buffer: "The most recent ‘next-error’ buffer. A buffer becomes most recent when its compilation, grep, or similar mode is started, or when it is used with \\[next-error]."
The fact that it's documented doesn't exactly mean that the behavior really makes sense or is optimal.
The problem occurred because two next-error buffer windows (*grep* and next-error capable ChangeLog) were both visible on the selected frame, but I believe we could fix this in the inner logic of next-error.
We've discussed the visibility-based selection before, I still don't think it makes sense, and the present bug report is evidence.
[Prev in Thread] | Current Thread | [Next in Thread] |