|
From: | Dmitry Gutov |
Subject: | bug#28864: 25.3.50; next-error-no-select does select |
Date: | Sat, 21 Oct 2017 00:49:11 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:56.0) Gecko/20100101 Thunderbird/56.0 |
On 10/20/17 10:21 AM, Tino Calancha wrote:
It kind of improves something, but the behavior is still wonky and counter-intuitive. Here are my steps:I think I understand it now: * change-log-mode sets 'next-error-last-buffer' to the current buffer (the ChangeLog source). We can restrict to not do that when we are calling 'next-error-no-select. I think some people don't like to use this-command in such situations; alternatively, we could use `change-log-mode-hook' but the patch below is shorter and explicit.
It's really a hack though, right? Maybe no major modes should set next-error-last-buffer by itself, no matter the current command.
I'd like to know what Juri thinks about this.
[Prev in Thread] | Current Thread | [Next in Thread] |