Re: Compile issues

[Dave Love]

address@hidden (Daniel Pfeiffer) writes:

> We are currently thinking about various remedies for this.  In the
> mean time start with M-x first-error.

I'm surprised it was installed if the normal user interface doesn't
work.

>> NEWS reports that `by default' warning messages are skipped, but gives
>> no indication of how to get the old behaviour back.  I think the old
>> behaviour should be the default.
>
> No way!  It states that only informationals are skipped.

OK, but I assumed it was lumping `information' and `warning' together,
since it's not clear to me that there's a useful distinction in
practice.  For instance, what would be warnings from GCC may appear as
`Info' from the DEC^WCopmpaq^WHP compilers though they're things you
need to see when trying to fix Emacs on Tru64.

Anyhow, if the facility to match them is there, it's not clear how to
enable it.

> It is only slightly incompatible.  Mostly tacking an '^' to the beginning of
> your regexps should be enough.

I think that should be documented.  What feature should external
packages test to know what version of messages they should use when
they have to support the released and new version?

> If you call a function called *-internal, you're bargaining for trouble :-)

Yes, but.  Several different packages in Emacs did that.  It appeared
to be sanctioned for that reason.  If it was wrong, one would expect
the first Emacs package that needed to do it to fix the issue.

> But the first arguments are emulated, except for the latter ones which had
> been added recently.  What is it that you need?

Probably.  I don't know about other people's use.  I will actually
submit a change to clean up the Erlang mode case, partly for other
reasons.