From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 65713@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#65713: compilation-next-error says: Moved past last error, even when none
Date: Sun, 03 Sep 2023 12:07:36 +0300 [thread overview]
Message-ID: <831qff8w13.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmzH-+p4w6VDF9oFX=NfLCBenMEoMicu0MCYdg8maeaOQ@mail.gmail.com> (message from Stefan Kangas on Sun, 3 Sep 2023 02:00:50 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 3 Sep 2023 02:00:50 -0700
> Cc: 65713@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> OK, there was no error, so instead of "Moved past last error" it should
> >> say "Didn't find any errors" when asked.
> >
> > FWIW, I don't see any need for such a feature. "Moved past the last
> > error" is correct even if there are no errors, and complicating the
> > code for such hair-splitting is not justified, IMO.
>
> The problem I see is that we're displaying a general message, when a
> more specific one could have been displayed instead. I'm not against
> fixing this minor blemish, if it can be done in a clean way.
Would it be enough to say something like
Moved past last error, if any
?
next prev parent reply other threads:[~2023-09-03 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 8:19 bug#65713: compilation-next-error says: Moved past last error, even when none Dan Jacobson
2023-09-03 8:45 ` Eli Zaretskii
2023-09-03 9:00 ` Stefan Kangas
2023-09-03 9:07 ` Eli Zaretskii [this message]
2023-09-03 14:07 ` Dan Jacobson
2023-09-03 14:40 ` Stefan Kangas
2023-09-04 22:57 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 11:15 ` Eli Zaretskii
2023-10-03 20:18 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-05 8:02 ` Eli Zaretskii
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=831qff8w13.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65713@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=stefankangas@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).