From: Ted Zlatanov <tzz@lifelogs.com>
To: bug-gnu-emacs@gnu.org
Subject: Re: bug#7351: 24.0.50; next-error no longer takes into account buffer modifications
Date: Mon, 06 Dec 2010 10:06:01 -0600 [thread overview]
Message-ID: <87ei9uhonq.fsf@lifelogs.com> (raw)
In-Reply-To: mailman.0.1289504684.29678.bug-gnu-emacs@gnu.org
On Thu, 11 Nov 2010 21:31:56 +0200 Paul Pogonyshev <pogonyshev@gmx.net> wrote:
PP> Glenn Morris wrote:
>> Paul Pogonyshev wrote:
>>
>> > I believe this used to work fine in past.
>>
>> Could you give a release of Emacs in which this works?
>>
>> I tried 21.4, 22.1, 22.2, 22.3, 23.1, and 23.2; and it didn't seem to
>> work in any of them.
PP> No. I seem to recollect that at some point (certainly before 24.x
PP> development, maybe even before 23) I could fix a compilation error in
PP> a C file by adding/removing lines, and subsequent errors would still
PP> be found correctly, without any line offset. Maybe it depends on
PP> actual error source, i.e. gcc vs. grep? Then again, maybe I invented
PP> this whole story and my memory is failing...
PP> In the latter case, can this be requalified as a feature request?
compilation-mode and the other providers of `next-error' set it up
differently (see `compilation-next-error-function'). I know that `M-x
occur' will track occurrences through add/delete changes, for instance,
but it has access to the original buffer. compilation-mode only has
access to line numbers at the time of the compilation.
Ted
prev parent reply other threads:[~2010-12-06 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 23:26 bug#7351: 24.0.50; next-error no longer takes into account buffer modifications Paul Pogonyshev
2010-11-11 0:49 ` Glenn Morris
2010-11-11 19:31 ` Paul Pogonyshev
2010-11-11 22:12 ` Jan Djärv
[not found] ` <mailman.0.1289504684.29678.bug-gnu-emacs@gnu.org>
2010-12-06 16:06 ` Ted Zlatanov [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ei9uhonq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=bug-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.