bug#65713: closed (compilation-next-error says: Moved past last error, even when none)

[GNU bug Tracking System]

Your message dated Thu, 05 Oct 2023 11:02:41 +0300
with message-id <83cyxt4hum.fsf@gnu.org>
and subject line Re: bug#65713: compilation-next-error says: Moved past last 
error, even when none
has caused the debbugs.gnu.org bug report #65713,
regarding compilation-next-error says: Moved past last error, even when none
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
65713: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65713
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> compilation-next-error says: Moved past last error, even when none
>
>
>
>
> Date: 
>
> Sun, 03 Sep 2023 03:19:30 -0500
>
>
>
>
> compilation-next-error says: Moved past last error
> even if there was no errors that it found.
> So it should differentiate such cases.
> M-x compile
>
> make
> make: *** No targets specified and no makefile found.  Stop.
>
> OK, there was no error, so instead of "Moved past last error" it should
> say "Didn't find any errors" when asked.
> emacs-version "29.1"
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#65713: compilation-next-error says: Moved past last error, even when none
>
>
>
>
> Date: 
>
> Thu, 05 Oct 2023 11:02:41 +0300
>
>
>
>
> > From: Rudolf Adamkovič <salutis@me.com>
> > Cc: jidanni@jidanni.org, 65713@debbugs.gnu.org
> > Date: Tue, 03 Oct 2023 22:18:06 +0200
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > >> Is it really correct to say that the point
> > >> "moved" when it did not move?
> > >
> > > Would it help to remove the "Moved" part?
> > 
> > That sounds like a good idea.
>
> Done on master, and closing the bug.
>
>
> --- End Message ---