mirror of
git://git.sv.gnu.org/emacs.git
synced 2025-12-27 07:41:28 -08:00
653eab4788
When matching messages in compilation-mode, keep track of the rule employed for each match. This facilitates debugging and allows us to verify that each test case really exercises the rule that we expect it to. Naturally this uncovered several test cases that didn't check what the author thought they did; the rules affixed to compile-tests--test-regexps-data are those actually used, so that the tests still pass. * lisp/progmodes/compile.el (compilation--message): Add 'rule' slot. (compilation-directory-properties, compilation-error-properties) (compilation-internal-error-properties, compilation-parse-errors) (compilation--compat-parse-errors): Set the rule slot. * test/lisp/progmodes/compile-tests.el (compile-tests--test-regexps-data) (compile-tests--grep-regexp-testcases) (compile-tests--grep-regexp-tricky-testcases): Add rules to test cases. (compile--test-error-line): Check that the rule matches what we expect. (compile-test-grep-regexps): Adapt to test case format. Remove now superfluous ert-info. |
||
|---|---|---|
| .. | ||
| cperl-mode-resources | ||
| flymake-resources | ||
| js-resources | ||
| ruby-mode-resources | ||
| asm-mode-tests.el | ||
| autoconf-tests.el | ||
| bat-mode-tests.el | ||
| cc-mode-tests.el | ||
| compile-tests.el | ||
| cperl-mode-tests.el | ||
| elisp-mode-tests.el | ||
| etags-tests.el | ||
| f90-tests.el | ||
| flymake-tests.el | ||
| glasses-tests.el | ||
| js-tests.el | ||
| opascal-tests.el | ||
| pascal-tests.el | ||
| ps-mode-tests.el | ||
| python-tests.el | ||
| ruby-mode-tests.el | ||
| scheme-tests.el | ||
| sql-tests.el | ||
| subword-tests.el | ||
| tcl-tests.el | ||
| xref-tests.el | ||