From: "Peter Münster" <pm@a16n.net>
To: help-gnu-emacs@gnu.org
Subject: problem with compilation-handle-exit
Date: Mon, 02 Oct 2023 17:40:36 +0200 [thread overview]
Message-ID: <87r0mduj63.fsf@a16n.net> (raw)
Hi,
When using latest ggtags.el (master) and latest emacs (also from
master), the last message in the compilation buffer is interpreted as an
info-message. Example:
--8<---------------cut here---------------start------------->8---
-*- mode: ggtags-global; default-directory: "~/.../" -*-
Global started at Mon Oct 2 17:23:19
global -v --result=grep --color=always --path-style=shorter --from-here=66:Src/Appli.c -- main
Src/Hex.c:57: main();
Src/crt0.s:96: call _main ; call user's main()
Src/crt0.s:273: call _main ; call the user's main()
3 objects located (using '/home/peter/.../GRTAGS').
Global found 3 references at Mon Oct 2 17:23:19, duration 0.03 s
--8<---------------cut here---------------end--------------->8---
The part "Global found 3 references at Mon Oct 2 17" is green and the
"23" is blue. So when invoking "next-error", instead of stopping after
the 3rd match with "Moved past last match", I get a question like
"Find this match in (default Global found 3 references at Mon Oct 2 17): ..."
But it seems, that compilation-handle-exit should avoid exactly this
misinterpretation, see comment in line 2496 of lisp/progmodes/compile.el:
";; Prevent that message from being recognized as a compilation error."
What would be the best method, to avoid this situation please?
TIA for any hints,
--
Peter
next reply other threads:[~2023-10-02 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 15:40 Peter Münster [this message]
2023-10-02 16:26 ` problem with compilation-handle-exit Eli Zaretskii
2023-10-03 6:47 ` Peter Münster
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=87r0mduj63.fsf@a16n.net \
--to=pm@a16n.net \
--cc=help-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.
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).