Re: Compile issues

[Dave Love]

Stefan Monnier <address@hidden> writes:

> Please send it to me and I'll install it.

Perhaps there was some reason it wasn't installed?

> Are these problems specific to the new compile.el or
> where they somehow absent in the old compile.el ?

The i18n issues are old, but it seems the right time to address i18n so
that you don't have to make potentially-incompatible changes in
future.  I realize that the current set of patterns doesn't look
amenable to a limited parameterization like it used to.

Issues with the new classification of the errors and redundancy are
new, but less important.

>>> If you tell us what the user does,
>> Types C-c C-k and then C-x `.
>
> Where?  When?  After which other command(s)?

C-c C-k compiles the buffer.  This isn't relevant --
`compilation-minor-mode' just doesn't work.  I assume the reason is
that font-locking just isn't set up:

(save-window-excursion
  (save-excursion
    (global-font-lock-mode 1)
    (comint-run "bash")
    (compilation-minor-mode)
    font-lock-keywords))
  => (t)

> You bet.  Looking at http://www.erlang.org/download/contrib/erlang.el (I
> assume that's what we're talking about),

I think that's an old version.  Mine came from the current OTP
distribution, probably via Debian.  (There's stuff in it which will
make you wince...)

> I don't see anything that would obviously break with the new code.

I don't know what's in the old version, but as I said, the current
version doesn't even work in the released Emacs.