Menu
▾
▴
#1 Error messages no longer Xemacs-compliant
Gary's commit of 5/21 changes
org.multijava.util.compiler.TokenReference to produce error
messages in the following format:
File "Error.java", line 3, character 12 error: Variable "a" is
not defined in current context
This change makes mjc much less usable under the default
installation of XEmacs up to and including 21.4 (and
possibly later versions as well), which doesn't support this
alternative syntax for error messages.
I am attaching a patch that adds a command-line option to
force old-style formatting.
patch adding command-line option for old-style messages
Logged In: YES
user_id=633675
It seems reasonable to have a command line option to
generate a different format for error messages.
Perhaps you can also add a .emacs file definition to do the
right thing with the standard options also?
Logged In: YES
user_id=26937
Here's a snippet of .emacs code that makes XEmacs recognize
the new-style mjc error messages:
(require 'compile)
(set-variable 'compilation-error-regexp-alist-alist
(cons
'(all
("\\File \"\\(.*\\)\", line \\([0-9]+\\), character \\([0-9]+\\).*:"
1 2 3))
compilation-error-regexp-alist-alist))
(compilation-build-compilation-error-regexp-alist)
This still does not provide syntax highlighting of the compilation
buffer, so I would still prefer the command-line option for
old-style messages. You can probably make XEmacs do syntax
highlighting too, but I haven't got the time to hack the elisp right
now.
Logged In: YES
user_id=26937
Note: SourceForge "helpfully" word-wrapped my last comment.
There should not be a newline in the string literal in the elisp
code I posted.
Logged In: YES
user_id=633675
Are you still interested in making this patch? If not,
you can close this, but if you are, change the code and
commit it, please.