From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@jurta.org>, Tino Calancha <tino.calancha@gmail.com>
Cc: 28864@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#28864: 25.3.50; next-error-no-select does select
Date: Sun, 29 Oct 2017 01:42:23 +0300 [thread overview]
Message-ID: <8c097da6-3396-0939-667c-cf50aafba689@yandex.ru> (raw)
In-Reply-To: <87wp3fxac4.fsf@localhost>
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 parent reply other threads:[~2017-10-28 22:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 13:07 bug#28864: 25.3.50; next-error-no-select does select Tino Calancha
2017-10-17 13:37 ` Dmitry Gutov
2017-10-17 14:17 ` Tino Calancha
2017-10-18 7:44 ` Dmitry Gutov
2017-10-20 7:21 ` Tino Calancha
2017-10-20 21:49 ` Dmitry Gutov
2017-10-21 3:52 ` Tino Calancha
2017-10-22 20:32 ` Juri Linkov
2017-10-22 22:29 ` Dmitry Gutov
2017-10-23 20:12 ` Juri Linkov
2017-10-23 20:23 ` Dmitry Gutov
2017-10-24 20:22 ` Juri Linkov
2017-10-24 22:23 ` Dmitry Gutov
2017-10-25 23:58 ` Dmitry Gutov
2017-10-28 21:07 ` Juri Linkov
2017-10-28 22:46 ` Dmitry Gutov
2017-10-29 21:42 ` Juri Linkov
2017-10-30 14:59 ` Dmitry Gutov
2017-10-30 18:30 ` Eli Zaretskii
2017-10-30 21:13 ` Dmitry Gutov
2017-10-30 21:15 ` Juri Linkov
2017-10-30 21:14 ` Juri Linkov
2017-10-31 0:02 ` Dmitry Gutov
2017-10-31 21:56 ` Juri Linkov
2017-10-31 23:42 ` Dmitry Gutov
2017-11-02 22:00 ` Juri Linkov
2017-11-05 13:37 ` Dmitry Gutov
2017-11-06 21:41 ` Juri Linkov
2017-10-28 20:54 ` Juri Linkov
2017-10-28 22:42 ` Dmitry Gutov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c097da6-3396-0939-667c-cf50aafba689@yandex.ru \
--to=dgutov@yandex.ru \
--cc=28864@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=npostavs@gmail.com \
--cc=tino.calancha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).