Open p-m opened 1 year ago
Hi @p-m,
Upstream may have changed something.
See the definition of (define-compilation-mode ggtags-global-mode...
which overrides a bunch of compilation-mode
variables. In particular, check compilation-error-regexp-alist
is correctly set and in ggtags-global-error-regexp-alist-alist
.
What I find really useful in dealing with similar situation is get a copy of compile.el
from 27
and master
and diff them to find suspicious changes.
In particular, check
compilation-error-regexp-alist
is correctly set and inggtags-global-error-regexp-alist-alist
.
Thanks. Indeed, after removing line 1685, it works. (The count is still wrong, but it's not really important.)
What I find really useful in dealing with similar situation is get a copy of
compile.el
from27
andmaster
and diff them to find suspicious changes.
Please find attached the diff. compile.el.diff.txt
Hi,
When using latest ggtags.el (master) and latest emacs (also from master), the last message in the compilation buffer is interpreted as a match. Example:
The part "G 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): ..."
How could I avoid this situation please?
Also, the counters in the mode-line are wrong: I get "7 0 0" instead of "3 0 0".
(With emacs-27.2, there is no problem, but the counters are "6 0 0".)
TIA for any hints, Peter