From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Pogonyshev <p.pogonyshev@anakreon.net>
Cc: 5620@debbugs.gnu.org
Subject: bug#5620: 23.1.92.1; next-error no longer takes into account buffer modifications
Date: Sat, 04 Dec 2021 22:00:20 +0100 [thread overview]
Message-ID: <87a6hg2ihn.fsf@gnus.org> (raw)
In-Reply-To: <201004281805.58350.p.pogonyshev@anakreon.net> (Paul Pogonyshev's message of "Wed, 28 Apr 2010 18:05:58 +0300")
Paul Pogonyshev <p.pogonyshev@anakreon.net> writes:
> I wonder if the supposed fix was checked at all. It fixes neither the
> original test case in the bug report, nor compilation error messages.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
The problem (as demonstrated by the original test case) is still present
in Emacs to this day. But it does seem to work sometimes, in my vague
recollection? Let's see...
Right, this is supposed to work by setting markers in the buffers where
you have the hits, so if you change the buffer in a way that doesn't
make the markers move, then you'll get the wrong line.
In this case:
foo
bar
baz
The marker is a 9, the start of the "baz" line. Then we yank two lines:
foo
bar
spam
ham
baz
But this doesn't make the "baz" marker move -- we're inserting before
that marker.
So I'm not sure how this could be fixed in general, as this is just the
way markers work. We could set the marker on the second char of the
line, perhaps, and that'd be marginally less likely to have this effect
(since people commonly insert new lines), but that seems like a pretty
gross hack.
So I don't know what, if anything, could be done here. Anybody?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next parent reply other threads:[~2021-12-04 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004281805.58350.p.pogonyshev@anakreon.net>
2021-12-04 21:00 ` Lars Ingebrigtsen [this message]
2022-01-21 13:47 ` bug#5620: 23.1.92.1; next-error no longer takes into account buffer modifications Lars Ingebrigtsen
2010-02-22 15:48 Paul Pogonyshev
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=87a6hg2ihn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=5620@debbugs.gnu.org \
--cc=p.pogonyshev@anakreon.net \
/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.