From: Dmitry Gutov <dgutov@yandex.ru>
To: Tino Calancha <tino.calancha@gmail.com>, 28864@debbugs.gnu.org
Subject: bug#28864: 25.3.50; next-error-no-select does select
Date: Tue, 17 Oct 2017 16:37:07 +0300 [thread overview]
Message-ID: <4045abe7-1acb-314b-b9ac-72b62db30570@yandex.ru> (raw)
In-Reply-To: <87bml72qck.fsf@gmail.com>
Hi!
On 10/16/17 4:07 PM, Tino Calancha wrote:
> X-Debbugs-CC: Dmitry Gutov <dgutov@yandex.ru>
I'm happy to commiserate, but it's hard to tell for me which part of
next-error* is broken for this use case. If not all of it, basically.
For instance, I don't understand why the patch at the end doesn't fix
the problem, and makes it worse instead (the behavior becomes less
predictable).
Why doesn't it? If we have to call next-error, and it normally changes
window configuration, save-selected-window seems like a natural fix.
> ;; Start emacs in the emacs root source dir
> emacs -Q
>
> M-x grep-find RET
> ;; Use following command:
> find . -type f -name ChangeLog\* -exec grep --color -nH -e baz {} +
> C-x o n ; This selects the source (shouldn't)
> ;; If doesn't select the source, try 'n' a few times more; eventually
> ;; you will be in the source.
It selects the source at the first try here, ever time.
Here's the patch that doesn't work:
diff --git a/lisp/simple.el b/lisp/simple.el
index 5ef511ce0a..16ac4b6788 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -325,8 +325,8 @@ next-error-no-select
select the source buffer."
(interactive "p")
(let ((next-error-highlight next-error-highlight-no-select))
- (next-error n))
- (pop-to-buffer next-error-last-buffer))
+ (save-selected-window
+ (next-error n))))
(defun previous-error-no-select (&optional n)
"Move point to the previous error in the `next-error' buffer and
highlight match.
next prev parent reply other threads:[~2017-10-17 13:37 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 [this message]
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
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=4045abe7-1acb-314b-b9ac-72b62db30570@yandex.ru \
--to=dgutov@yandex.ru \
--cc=28864@debbugs.gnu.org \
--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).