From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 65713@debbugs.gnu.org
Subject: bug#65713: compilation-next-error says: Moved past last error, even when none
Date: Sun, 03 Sep 2023 11:45:43 +0300 [thread overview]
Message-ID: <838r9n8x1k.fsf@gnu.org> (raw)
In-Reply-To: <87o7ij7jot.8.fsf@jidanni.org> (message from Dan Jacobson on Sun, 03 Sep 2023 03:19:30 -0500)
> From: Dan Jacobson <jidanni@jidanni.org>
> 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.
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.
So my vote is to close this as "wontfix".
next prev parent reply other threads:[~2023-09-03 8:45 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 [this message]
2023-09-03 9:00 ` Stefan Kangas
2023-09-03 9:07 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838r9n8x1k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65713@debbugs.gnu.org \
--cc=jidanni@jidanni.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.