From: Ari Roponen <ari.roponen@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9679@debbugs.gnu.org
Subject: bug#9679: 24.0.90; After rgrep, next-error goes to the wrong line
Date: Fri, 07 Oct 2011 11:41:38 +0300 [thread overview]
Message-ID: <m3k48hurb1.fsf@gmail.com> (raw)
In-Reply-To: <m3fwj58jqy.fsf@gmail.com> (Ari Roponen's message of "Fri, 07 Oct 2011 08:15:49 +0300")
Ari Roponen <ari.roponen@gmail.com> writes:
> I guess the problem has something to do with those markers.
I found a way to fix the problem locally without reverting any commits.
The function `compilation-next-error-function' contains this:
;; If loc contains no marker, no error in that file has been visited.
;; If the marker is invalid the buffer has been killed.
;; So, recalculate all markers for that file.
(unless (and (compilation--loc->marker loc)
(marker-buffer (compilation--loc->marker loc))
;; FIXME-omake: For "omake -P", which automatically recompiles
;; when the file is modified, the line numbers of new output
;; may not be related to line numbers from earlier output
When I add "nil" after "and", the problem goes away.
--
Ari Roponen
next prev parent reply other threads:[~2011-10-07 8:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r4uwybeh.fsf@gnu.org>
2011-10-06 6:14 ` bug#9679: 24.0.90; After rgrep, next-error goes to the wrong line Ari Roponen
2011-10-06 15:27 ` Juri Linkov
2011-10-07 5:15 ` Ari Roponen
2011-10-07 8:41 ` Ari Roponen [this message]
2011-10-07 15:20 ` Juri Linkov
2011-10-07 15:51 ` Ari Roponen
2011-10-07 16:36 ` Juri Linkov
2011-10-07 17:48 ` Ari Roponen
2011-10-08 16:30 ` Juri Linkov
2011-10-09 5:38 ` Ari Roponen
2012-05-06 6:23 ` Ari Roponen
[not found] ` <handler.9679.C.13363577086087.notifdonectrl.0@debbugs.gnu.org>
2012-05-13 6:39 ` bug#9679: acknowledged by developer (close 9679) Ari Roponen
2012-05-13 9:18 ` Chong Yidong
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=m3k48hurb1.fsf@gmail.com \
--to=ari.roponen@gmail.com \
--cc=9679@debbugs.gnu.org \
--cc=juri@jurta.org \
/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).