unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* problem with compilation-handle-exit
@ 2023-10-02 15:40 Peter Münster
  2023-10-02 16:26 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Münster @ 2023-10-02 15:40 UTC (permalink / raw)
  To: help-gnu-emacs

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




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: problem with compilation-handle-exit
  2023-10-02 15:40 problem with compilation-handle-exit Peter Münster
@ 2023-10-02 16:26 ` Eli Zaretskii
  2023-10-03  6:47   ` Peter Münster
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2023-10-02 16:26 UTC (permalink / raw)
  To: help-gnu-emacs

> From: Peter Münster <pm@a16n.net>
> Date: Mon, 02 Oct 2023 17:40:36 +0200
> 
> 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?

Make sure ggtags.el does the same at the end as
compilation-handle-exit?



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: problem with compilation-handle-exit
  2023-10-02 16:26 ` Eli Zaretskii
@ 2023-10-03  6:47   ` Peter Münster
  0 siblings, 0 replies; 3+ messages in thread
From: Peter Münster @ 2023-10-03  6:47 UTC (permalink / raw)
  To: help-gnu-emacs

On Mon, Oct 02 2023, Eli Zaretskii wrote:

> Make sure ggtags.el does the same at the end as
> compilation-handle-exit?

compilation-handle-exit is called, so I guess, that ggtags does not need
to do the same. But anyway, I guess, that the problem is indeed
somewhere in ggtags.el because there is no such problem when compiling a
C-file. I'll send a bug-report...

-- 
           Peter




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-10-03  6:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-02 15:40 problem with compilation-handle-exit Peter Münster
2023-10-02 16:26 ` Eli Zaretskii
2023-10-03  6:47   ` Peter Münster

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).